Ensure the thread suspended event is fired even if the thread was suspended when its NB model was being created. #8232
+119
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the VS Code extension and running this code under debugger:
(having the line breakpoint on the marked line). The debugger does not properly stop at the breakpoint.
What I think is happening is that when the
JPDAThreadImpl
is created, it is already suspended inside the debuggee. As a consequence, the event that the thread was suspended does not go through, and the "UI" part of the debugger is not notified the thread was suspended.The proposal here is to send the "thread suspended" event the first time the thread stops on a breakpoint, if it was created as already-suspended.