microsoft / microsoft/vscode-cpptools
externalTerminal console does not launch when path includes spaces
Open
Nobody has claimed this yet.
bug
Language Service
Visual Studio Code
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Bug
- Create a debug launch configuration that uses the
externalTerminalconsole 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with a selected externalTerminal debug configuration on Windows, using a path that contains spaces, and compare the reported launch command with one using a path without spaces. Start from the externalTerminal debugger launch path; done means the external window launches successfully and the target application starts without the quoting error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100