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

It is not possible to see any error output from crashed debug adapter extension #40198

Closed
omusil24 opened this issue Dec 14, 2017 · 2 comments
Closed
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@omusil24
Copy link

omusil24 commented Dec 14, 2017

  • VSCode Version: Code 1.18.1 (929bacb, 2017-11-16T18:34:22.110Z)
  • OS Version: Linux x64 4.10.0-42-generic
  • Extensions:
Extension Author (truncated) Version
swagger-viewer Arj 1.5.0
Bookmarks ale 0.18.0
cpptools ms- 0.14.4
swaggitor qns 0.1.1
qore-vscode qor 0.2.6
cmake twx 0.0.17

(2 theme extensions excluded)


I am developing a debug adapter extension but even through extensive logging, it's sometimes hard to find problems when the debug adapter crashes because VS Code just shows an error message Debug adapter process has terminated unexpectedly. There's no output in any of the terminals and debug consoles. It would be very useful if VS Code showed the exit code and stderr output which was produced by the debug adapter.

Steps to Reproduce:

  1. Create a debug adapter extension.
  2. Start debugging it.
  3. Try to debug some file using it.
  4. Make the debug adapter crash.

Reproduces without extensions: Yes

@vscodebot vscodebot bot added the debug Debug viewlet, configurations, breakpoints, adapter issues label Dec 14, 2017
@isidorn isidorn added this to the December 2017/January 2018 milestone Dec 15, 2017
@omusil24
Copy link
Author

Just found out that in the [Extension Development Host] window, in the Extensions tab of the Output terminal, there's stderr output. I guess this makes this issue solved.

But nonetheless, if VS Code opened this terminal tab in case of extension crash automatically, it would be useful. Or if it somehow made it more visible that there's a tab of the terminal with new unread output.

@isidorn
Copy link
Contributor

isidorn commented Jan 5, 2018

Dup of #41190

@isidorn isidorn closed this as completed Jan 5, 2018
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 5, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 20, 2018
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 *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants