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

Breakpoint stopped event will cause all threads 'PAUSED ON BREAKPOINT' #34437

Closed
testforstephen opened this issue Sep 15, 2017 · 1 comment
Closed

Breakpoint stopped event will cause all threads 'PAUSED ON BREAKPOINT' #34437

testforstephen opened this issue Sep 15, 2017 · 1 comment
Assignees
@isidorn
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone
September 2017

Comments

@testforstephen
Copy link

  • VSCode Version: 1.17.0-insider
    image

When developing java debugger, it supports breakpoint hit event only suspends a single thread and keeps other threads running. So for breakpoint hit event, our java debugger will send a stopped DA event with allThreadsStopped flag as false. See {"event":"stopped","body":{"threadId":1,"reason":"breakpoint","allThreadsStopped":false,"type":"stopped"},"seq":11,"type":"event"}. But vscode shows all threads are PAUSED ON BREAKPOINT.
image

I remember vscode works before, and it will only display PAUSED ON BREAKPOINT on the related thread. It seems a regression bug.
@vscodebot vscodebot bot added the insiders label Sep 15, 2017
@vscodebot vscodebot bot added the debug Debug viewlet, configurations, breakpoints, adapter issues label Sep 15, 2017
@isidorn isidorn added this to the September 2017 milestone Sep 15, 2017
@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Sep 15, 2017
@chrmarti chrmarti removed the insiders label Sep 27, 2017
@isidorn
Copy link
Contributor

isidorn commented Sep 28, 2017 •
edited

@testforstephen I have pushed a fix for this, you can pick it up from a latest build here https://vscode-builds.azurewebsites.net/builds/insider
Let us know if it works for you

note: builds will only be available in 4,5 hours, the latest build does not contiain the fix at the moment

@aeschli aeschli added the verified Verification succeeded label Sep 29, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 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 verified Verification succeeded
Projects
None yet
Milestone
September 2017
Development

No branches or pull requests
4 participants
@isidorn @aeschli @chrmarti @testforstephen