-
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: setting breakpoint while running causes skipped stopped event at next breakpoint #759
Labels
Debug
Issues related to the debugging functionality of the extension.
FrozenDueToAge
release-blocker
must be fixed before the next release.
Comments
polinasok
added
the
Debug
Issues related to the debugging functionality of the extension.
label
Oct 9, 2020
Change https://golang.org/cl/261078 mentions this issue: |
Change https://golang.org/cl/262257 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Oct 14, 2020
There were some issues caused by not sending a stopped event to the client every time that the continue callback was called. This change reverts the logic to skip calling handleReenterDebug in order to get back to a state where the debugger issues stopped events every time. This should fix issues with the debugger appearing to be running when it is stopped. Updates #149, #172, and #759 Change-Id: I70aae05bc3bf50499b046594a43d972ec01091cf Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/262257 Run-TryBot: Suzy Mueller <suzmue@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com> Trust: Suzy Mueller <suzmue@golang.org> Trust: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
I believe this has been fixed by the CL that reverted the original change that caused this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Debug
Issues related to the debugging functionality of the extension.
FrozenDueToAge
release-blocker
must be fixed before the next release.
This is cause by https://golang.org/cl/253578.
This came up as part of remote Theia debugging by @quoctruong (see https://golang.org/cl/257337).
I was able to reproduce this locally at HEAD (7d5f58a).
Steps to reproduce
Launch.json
Logs with detailed explanations
After:
Before:
The text was updated successfully, but these errors were encountered: