when I ran this test, put the breakpoint to fmt.Println this statement

    func TestName(t *testing.T) {
            fmt.Println("123")
        }

it jumped to proc.go every time, how can I solve this problem?

Tried to update delve(dlv), put it to goland custom propertity, but it didn't work

My Go version: 1.22.7 GoLand version: 2024.3.5

when I ran this test, put the breakpoint to fmt.Println this statement

    func TestName(t *testing.T) {
            fmt.Println("123")
        }

it jumped to proc.go every time, how can I solve this problem?

Tried to update delve(dlv), put it to goland custom propertity, but it didn't work

My Go version: 1.22.7 GoLand version: 2024.3.5

• go
• ide
• goland

• I did a clean install og Go with Homebrew (MacOS) and Delve (go install) today. I'm getting the exact same behaviour - both in GoLand and VSCode. They both ignore the breakpoint and stops at the gopark function inside proc.go. If no breakpoint is set, it runs green. To be clear: It never stops at any user set breakpoint. – Tormod Haugene Commented yesterday
• Related: github/golang/vscode-go/issues/3743 – Tormod Haugene Commented yesterday

1 Answer 1

Stepping into the Go SDK's internals after the program finishes is expected in this case. The debugger continues to operate even after your program's code has completed. We are considering a feature to hide these internal debugger steps from the user if the user requests it, so it appears that the debugger stops cleanly after your program finishes. Here is a feature request tracking this improvement: https://youtrack.jetbrains/issue/GO-10534