Closed
Description
What version of Go, VS Code & VS Code Go extension are you using?
- Run
go version
to get version of Go from the VS Code integrated terminal.
go 1.16.5 darwin/amd64 - Run
gopls -v version
to get version of Gopls from the VS Code integrated terminal.
golang.org/x/tools/gopls v0.7.0
golang.org/x/tools/[email protected] h1:JQBHW81Gsyim6iDjUwGoPeSpXrSqwen3isPJLfDfaYU= - Run
code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.
1.58.0
2d23c42a936db1c7b3b06f918cde29561cc47cd6
x64 - Check your installed extensions to get the version of the VS Code Go extension
v0.26.0 - Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) >
Go: Locate Configured Go Tools
command.
Share the Go related settings you have added/edited
{
"workbench.editor.highlightModifiedTabs": true,
"go.delveConfig": {
"dlvLoadConfig": {
"followPointers": true,
"maxVariableRecurse": 1,
"maxStringLen": 1024,
"maxArrayValues": 64,
"maxStructFields": -1
},
"apiVersion": 2,
"showGlobalVariables": false
}
}
Describe the bug
When debugging VS Code jumps to proc.go
on every step. This started after updating VS Code to June 2021 (version 1.58).
Steps to reproduce the behavior:
Load up a project, starting debugging.