Skip to content

Conversation

@mfussenegger
Copy link
Owner

Some debug adapters allow to resume execution using custom evaluate
commands. This unfortunately by-passes some logic that puts the client
into "running" state again.

If the client then receives a stopped event it assumed it
was already stopped and sent a continue request (unless
auto_continue_if_many_stopped was disabled)

This changes the condition to also jump if stopped_thread_id == stopped.threadId

Closes #898

Co-authored-by: xac [email protected]

Some debug adapters allow to resume execution using custom evaluate
commands. This unfortunately by-passes some logic that puts the client
into "running" state again.

If the client then receives a stopped event it assumed it
was already stopped and sent a continue request (unless
`auto_continue_if_many_stopped` was disabled)

This changes the condition to also jump if `stopped_thread_id ==
stopped.threadId`

Closes #898

Co-authored-by: xac <[email protected]>
@mfussenegger mfussenegger merged commit 5e1e259 into master Mar 15, 2023
@mfussenegger mfussenegger deleted the stop-and-jump-same-thread branch March 15, 2023 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Program suddenly exit when call si or n or other continue command in repl.

2 participants