-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging Hangs when default terminal app doesn't exist #67296
Comments
Ref some background information as it pertains to folks using native VS Code on WSL here. It might be that the console/terminal application doesn't exist, as the steps above and issue title suggest. More typically the |
@weinand This is becoming a bigger issue especially in the VS Code remote scenario as it doesn't fail with a good message to the user. Can we prioritize this to be fixed? |
@pieandcakes this issue had been partially addressed in VS Code but it still needs some work on the extension side. Please see microsoft/vscode-remote-release#381. |
@pieandcakes I've fixed the broken link... |
Thanks. I look forward to testing it. |
Heads up I am still seeing situations where you get the "hang" with |
To test: Set Terminal.External.LinuxExec to an app that doesn't exist.
Start debugging with external terminal (I used the C++ extension and set
externalConsole
totrue
).Expected:
Failure response for RunInTerminal command.
Actual:
No Response from VS Code's debugadapter protocol.
UI looks like it is waiting for debugging to start.
The text was updated successfully, but these errors were encountered: