Skip to content
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

Closed
pieandcakes opened this issue Jan 28, 2019 · 6 comments
Closed

Debugging Hangs when default terminal app doesn't exist #67296

pieandcakes opened this issue Jan 28, 2019 · 6 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@pieandcakes
Copy link
Contributor

pieandcakes commented Jan 28, 2019

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 to true).

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.

@therealkenc
Copy link

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 x-terminal-emulator app (on Ubuntu, usually gnome-terminal) exists aight, but can fail to run for reasons which are easy to trip over in our quirky environment. Any feedback the user can get (even the nonzero error code returned from the app) would go a long way.

@pieandcakes
Copy link
Contributor Author

@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?

@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label May 8, 2019
@weinand
Copy link
Contributor

weinand commented May 8, 2019

@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.

@weinand
Copy link
Contributor

weinand commented May 20, 2019

@pieandcakes I've fixed the broken link...

@pieandcakes
Copy link
Contributor Author

Thanks. I look forward to testing it.

@therealkenc
Copy link

Heads up I am still seeing situations where you get the "hang" with externalConsole=false (the internal console) but the external console works fine. This is on 1.35.0-insider 2019-05-17 on Real Linux Ubuntu to Real Linux Ubuntu with Remote SSH, but I saw the behavior last December-February too without inviting Remote to the party. Unfortunately it is really hard to give definitive repro steps to get in that state, because there are so many moving parts. And I know that doesn't help you. I am hoping that whatever error UX is forthcoming might shed some light. Mentioning it because if I've hit it you'll probably hear from someone else eventually too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

No branches or pull requests

3 participants