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

do not attach to node.js processes that are already being debugged #57232

Closed
weinand opened this issue Aug 26, 2018 · 1 comment
Closed

do not attach to node.js processes that are already being debugged #57232

weinand opened this issue Aug 26, 2018 · 1 comment
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@weinand
Copy link
Contributor

weinand commented Aug 26, 2018

If node.js debugging is started via a launch config which uses the integrated terminal and if auto-attach mode is enabled, VS Code tries to attach to the already debugged node.js process another time (which results is a timeout error).

The problem is that auto-attach cannot easily detect whether a node.js in debug mode was launched manually by the user or via a launch config.

@weinand weinand added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Aug 26, 2018
@weinand weinand added this to the August 2018 milestone Aug 26, 2018
@weinand weinand self-assigned this Aug 26, 2018
@weinand
Copy link
Contributor Author

weinand commented Aug 27, 2018

duplicate of #49403

@isidorn isidorn added *duplicate Issue identified as a duplicate of another issue(s) and removed bug Issue identified by VS Code Team member as probable bug labels Aug 30, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 10, 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