externalTerminal console does not launch when path i... | microsoft/vscode-cpptools

Nessuno ha ancora preso questa issue.

Type: Bug

Create a debug launch configuration that uses the externalTerminal console type and make it the currently selected debug configuration.
Launch the debugger.
An external window will appear with an error message similar to this (note the quoting of path elements with spaces):

[error 2147942402 (0x80070002) when launching `Lins\AppData\Local\Microsoft\WindowsApps\wt.exe 
-d C:\WINDOWS\System32\cmd.exe /c c:\Users\Adam "Lins\.vscode\extensions\ms-vscode.cpptools-1.18.5-win32-x64\debugAdapters\vsdbg\bin\VsDebugConsole.exe 
\\.\pipe\Microsoft-VisualStudio-Debug-Console-{4378F327-15AB-4D47-BC0B-45CB6D2FF806} 
Local\{4378F327-15AB-4D47-BC0B-45CB6D2FF806} /AutoExit & pause"']

In VSCode, the debug control panel will appear as well as an error message pop-up noting that the target application cannot be started.

Extension version: 1.18.5
VS Code version: Code 1.86.1 (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:08:20.941Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-1265U (12 x 2688)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	15.44GB (5.34GB free)
Process Argv	..\..\.local\tenpo.code-workspace --crash-reporter-id 0312ea16-4d0d-401e-92c7-0bd47ce3b3fd
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
b5d27386:30958190
a89i1917:30961429
3ef8e399:30964150
e3gdj431:30958358

Riproduci il problema con una configurazione di debug externalTerminal selezionata su Windows, utilizzando un percorso che contiene spazi, e confronta il comando di avvio riportato con uno che utilizza un percorso senza spazi. Inizia dal percorso di avvio del debugger externalTerminal; il lavoro è completato quando la finestra esterna viene avviata correttamente e l'applicazione di destinazione si avvia senza l'errore di quoting.

Scritto dal modello di indicizzazione a partire dal testo della issue.

externalTerminal console does not launch when path includes spaces

Descrizione

Guida per i contributori

Come iniziare

Direzione di ricerca

Valutazione