Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Attempt to fix the debugger jumping to gopark #2207

Merged
merged 2 commits into from
Dec 31, 2018

Conversation

segevfiner
Copy link
Contributor

@segevfiner segevfiner commented Dec 24, 2018

According to the spec you are first supposed to acknowledge the command and only than send the stopped event. Changing this seems to have fixed the jumping to gopark/proc.go for me. Please test that this works.

Debugging is still really slow, but that's a different issue, VS Code is simply requesting, and receiving, way too much information from delve on each step.

See: Debug Adapter Protocol Specification - Next Request.

Possible fix for #2133

this.handleReenterDebug('breakpoint');
});
this.sendResponse(response);
verbose('ContinueResponse');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The verbose call for logging should move as well

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Dec 31, 2018

@segevfiner I am using
https://play.golang.org/p/nYkRp-yG1aK (breakpoint in the Println line) which has the jump to proc.go issue. The fix in this PR doesn't fix the jump for me.

Regardless, I believe this is a change we should make anyway. The response should be sent by the adapter only after the call to delve completes.

@segevfiner
Copy link
Contributor Author

segevfiner commented Dec 31, 2018

@segevfiner I am using
https://play.golang.org/p/nYkRp-yG1aK (breakpoint in the Println line) which has the jump to proc.go issue. The fix in this PR doesn't fix the jump for me.

Darn... Guess we'll have to keep digging...

@ramya-rao-a ramya-rao-a merged commit 456fdab into microsoft:master Dec 31, 2018
@segevfiner segevfiner deleted the gopark-debug-jump-bug branch December 31, 2018 21:32
segevfiner added a commit to segevfiner/vscode-go that referenced this pull request Dec 31, 2018
ramya-rao-a pushed a commit that referenced this pull request Jan 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants