Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Occasional debug fails to start w/o message on Windows w/ Node v6.6.0 (32-bit) #29

Closed
mousetraps opened this issue Sep 27, 2016 · 2 comments

Comments

@mousetraps
Copy link

Testing microsoft/vscode#12600
Occasionally, debugging fails to launch w/o much indication as to why.

F5 to launch, debug bar flashes, then quickly disappars as the following message is printed to the debug console:

node --inspect=6952 --debug-brk --nolazy server.js 
Debugger listening on port 6952.
Warning: This is an experimental feature and could change at any time.

will update w/ better repro steps if available, but might be good to add some better logging to account for issues like this in the future

@roblourens
Copy link
Member

Can you set 'verboseDiagnosticLogging': true in your launch config next time? There will probably be some error

@roblourens
Copy link
Member

Probably a crash same as #38. The assert message doesn't go to stderr so I'm not sure how to show more info in the debug console.

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 29, 2018
Shenniey pushed a commit to Shenniey/vscode-node-debug2 that referenced this issue Nov 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants