-
Notifications
You must be signed in to change notification settings - Fork 752
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
debug: changing to a different goroutine and executing Step Over goes back to the previous goroutine #118
Comments
There is a TODO for this in dlv-dap as well: |
Change https://golang.org/cl/300769 mentions this issue: |
…epping The debugger needs to switch to the correct goroutine if the threadId in the request does not match the current goroutine. This change checks the current state to decide if it should switch goroutines, and then does so. This adds a test for 'next' and 'step in' requests that switch goroutines. Updates #118 Change-Id: I553ebbed6de1001e0e7da756278fcc717884f946 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/300769 Trust: Suzy Mueller <suzmue@golang.org> Run-TryBot: Suzy Mueller <suzmue@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: kokoro <noreply+kokoro@google.com>
Change https://golang.org/cl/306989 mentions this issue: |
The switch goroutine feature has now been merged into dlv dap so the behavior can be included in the extension tests. Updates #118 Change-Id: I1258eae502abcd7665887f5a225407e0fd1bd2a6 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/306989 Trust: Suzy Mueller <suzmue@golang.org> Run-TryBot: Suzy Mueller <suzmue@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Was about to close this, but you beat me to it! Thank you for making the change @suzmue! Just tried it for myself - works great! |
From microsoft/vscode-go#2560 by @aarzilli:
main.coroutine
in the left columnExpected:
Cursor moves to the next line on the goroutine I'm currently watching.
What actually happend
Debuggers switches back to the goroutine it was originally stopped at and moves to the next line.
The text was updated successfully, but these errors were encountered: