Open FavonianKong opened 3 years ago
There is an issue with VS Code launching an external window with WSL. This would need to be investigated since we request RunInTerminal with external console, but they may be reporting that the window is succeeding.
This issue has been closed automatically because it's labeled as 'external'.
This issue has been closed automatically because it has not had recent activity.
It seems this bug have not been resolved, is anyone handling it?
related issue: #1772
yes indeed. the issue is still bothering me.
I also meet this problem. After I update vscode to the newest edition, Set externalConsole to true doesn't work.
Same problem here. externalConsole true = application doesn't run, debugger hangs. Set to false it doesn't output at all.
Not using wsl it works fine so it definitely is a wsl/vscode problem.
Same problem here.... It's so convenient to close issues automatically when there is no recent activity. Problems just go away, it's magic !!
I am also having the same issue!
3 years later... hello?
Is this not identical to https://github.com/microsoft/vscode-cpptools/issues/1772? And this one should thus be closed.
Both seem to be about WSL and "externalConsole": true
not working.
pls help! "externalConsole": true
is definitely not working
Type: Debugger
Describe the bug
Other extensions you installed (and if the issue persists after disabling them):
There's no special software.
A clear and concise description of what the bug is.
When I set
externalConsole
inlaunch.json
totrue
, pressing F5 will fail to start the debugger, the debugger just hangs. IfexternalConsole
is set tofalse
, the debug function works fine, but instructions inDEBUG CONSOLE
e.g.bt
orp var
are invalid. What a dilemma it is :(To Reproduce Please include a code sample and
launch.json
configuration.I've seen similar problems in the VsCode community, and they think the problem is caused by extension. Any idea?https://github.com/microsoft/vscode/issues/111160#issuecomment-732000615