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.

Sign up for GitHub

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

Jump to bottom

state of debug actions does not reflect debug state #37134

Closed
weinand opened this issue Oct 30, 2017 · 1 comment
Closed

state of debug actions does not reflect debug state #37134

weinand opened this issue Oct 30, 2017 · 1 comment
Assignees
@isidorn
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority verified Verification succeeded
Milestone
October 2017

Comments

@weinand
Copy link
Contributor

weinand commented Oct 30, 2017 •
edited

For concurrent node-debug sessions I'm seeing that the debugger is confused about the debug state. The CALL STACK view and the editor both indicate that the debugger is stopped but the debug actions think that the debugger is running:

2017-10-30_12-47-19

In this case I've started the node-debug server first and then launched the mocha tests as another session.

When launching the mocha tests from the terminal (hence no second debug session was created) this problem did not occur.
@weinand weinand added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority labels Oct 30, 2017
@weinand weinand added this to the October 2017 milestone Oct 30, 2017
@isidorn
Copy link
Contributor

isidorn commented Oct 30, 2017

@weinand great catch, thanks!

egamma pushed a commit that referenced this issue Oct 31, 2017
@isidorn @egamma
debug: better previous state computation to only fire update state in…
769680f 
… case of an actual change

fixes #37134
@weinand weinand added the verified Verification succeeded label Oct 31, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 14, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Milestone
October 2017
Development

No branches or pull requests
2 participants
@weinand @isidorn