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

debug: "unable to display threads: detached from the process" #149

Closed
stamblerre opened this issue Jun 2, 2020 · 5 comments
Closed

debug: "unable to display threads: detached from the process" #149

stamblerre opened this issue Jun 2, 2020 · 5 comments
Labels
debug/legacy legacy debug adapter related issues - new issues won't be fixed Debug Issues related to the debugging functionality of the extension. FrozenDueToAge
Milestone
vscode-go/unplanned

Comments

@stamblerre
Copy link
Contributor

Transferring this issue from microsoft/vscode-go#3104 - see the repro case provided in microsoft/vscode-go#3104 (comment).

/cc @polinasok
@stamblerre stamblerre mentioned this issue Jun 2, 2020
Closed
@stamblerre stamblerre added the Debug Issues related to the debugging functionality of the extension. label Jun 3, 2020
@segevfiner
Copy link
Contributor

I'm seeing this pretty consistently whenever I restart or stop debugging.

macOS 10.14.6
Go 1.14.5
Delve 1.4.1
VS Code 1.47.2
vscode-go 0.15.1

@polinasok
Copy link
Contributor

I think this is caused by the same flaw in the logic that causes #172. We need to fix continue logic not to always assume that execution was stopped on a breakpoint.

@gopherbot
Copy link
Collaborator

Change https://golang.org/cl/253578 mentions this issue: src/debugAdapter: send stopped events from continue on breakpoint only

@gopherbot
Copy link
Collaborator

Change https://golang.org/cl/262257 mentions this issue: src/debugAdapter: revert cl/253578

gopherbot pushed a commit that referenced this issue Oct 14, 2020
@suzmue
src/debugAdapter: revert cl/253578
6703469 
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>
@suzmue suzmue reopened this Oct 14, 2020
@gopherbot gopherbot added this to the Untriaged milestone Apr 8, 2021
@hyangah hyangah modified the milestones: Untriaged, Backlog Apr 14, 2021
@suzmue
Copy link
Contributor

suzmue commented Dec 22, 2021

This bug does not appear in the dlv dap DA and we do not plan to fix this in the legacy adapter.

@suzmue suzmue closed this as completed Dec 22, 2021
@polinasok polinasok added debug/legacy legacy debug adapter related issues - new issues won't be fixed WillNotFix and removed DA: DlvDAP labels Dec 30, 2021
@golang golang locked and limited conversation to collaborators Dec 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
debug/legacy legacy debug adapter related issues - new issues won't be fixed Debug Issues related to the debugging functionality of the extension. FrozenDueToAge
Projects
None yet
Milestone
vscode-go/unplanned
Development

No branches or pull requests
6 participants
@hyangah @stamblerre @suzmue @gopherbot @segevfiner @polinasok