microsoft / microsoft/vscode-cpptools
Empty window opens with internalConsole during debug
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Bug type: Debugger
Describe the bug
- OS and Version: Windows 10 20H2
- VS Code Version: 1.56.2
- C/C++ Extension Version: 1.4.0-insiders
After setting the launch.json as the following, an external window is opened at debug. All output appears in the debug console, but an empty console window is there.
"version": "0.2.0",
"configurations": [
{
"name": "Debug (win)",
"type": "cppvsdbg",
"request": "launch",
"program": "${command:cmake.launchTargetPath}",
"args": [ ],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"console": "internalConsole",
"internalConsoleOptions": "openOnSessionStart"
}
I looked up the documentation for the launch.json, but there is no mention of "console" option, only the old "externalConsole" option is there, which is deprecated.
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 using the shown launch.json configuration with cppvsdbg, console set to internalConsole, and internalConsoleOptions set to openOnSessionStart. Trace how these options are handled during a debug launch and verify that no empty external console window opens while output remains in the debug console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, typescript, vscode
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100