delve/_fixtures/decllinetest.go

package main

import (
	"fmt"
)

func main() {
	a := 0
	a++
	b := 0
	f1(a, b)
}

func f1(
	a int,
	b int,
) {
	fmt.Printf("%d %d\n", a, b)
}
pkg/proc: use DW_AT_decl_line to determine var visibility Fixes #186, #83 2017-09-08 10:31:03 +00:00			`package main`

			`import (`
			`"fmt"`
			`)`

			`func main() {`
			`a := 0`
			`a++`
			`b := 0`
Go 1.15 support (#2011) * proc: start variable visibility one line after their decl line In most cases variables shouldn't be visible on their declaration line because they won't be initialized there. Function arguments are treated as an exception. This fix is only applied to programs compiled with Go 1.15 or later as previous versions of Go did not report the correct declaration line for variables captured by closures. Fixes #1134 * proc: silence go vet error * Makefile: enable PIE tests on windows/Go 1.15 * core: support core files for PIEs on windows * goversion: add Go 1.15 to supported versions * proc: fix function call injection for Go 1.15 Go 1.15 changed the call injection protocol so that the runtime will execute the injected call on a different (new) goroutine. This commit changes the function call support in delve to: 1. correctly track down the call injection state after the runtime switches to a different goroutine. 2. correctly perform the escapeCheck when stack values can come from multiple goroutine stacks. * proc: miscellaneous fixed for call injection under macOS with go 1.15 - create copy of SP in debugCallAXCompleteCall case because the code used to assume that regs doesn't change - fix automatic address calculation for function arguments when an argument has a spurious DW_OP_piece at entry 2020-07-28 16:19:51 +00:00			`f1(a, b)`
			`}`

dwarf: ignore DeclLine for function args (#3400) 2023-05-31 16:58:47 +00:00			`func f1(`
			`a int,`
			`b int,`
			`) {`
Go 1.15 support (#2011) * proc: start variable visibility one line after their decl line In most cases variables shouldn't be visible on their declaration line because they won't be initialized there. Function arguments are treated as an exception. This fix is only applied to programs compiled with Go 1.15 or later as previous versions of Go did not report the correct declaration line for variables captured by closures. Fixes #1134 * proc: silence go vet error * Makefile: enable PIE tests on windows/Go 1.15 * core: support core files for PIEs on windows * goversion: add Go 1.15 to supported versions * proc: fix function call injection for Go 1.15 Go 1.15 changed the call injection protocol so that the runtime will execute the injected call on a different (new) goroutine. This commit changes the function call support in delve to: 1. correctly track down the call injection state after the runtime switches to a different goroutine. 2. correctly perform the escapeCheck when stack values can come from multiple goroutine stacks. * proc: miscellaneous fixed for call injection under macOS with go 1.15 - create copy of SP in debugCallAXCompleteCall case because the code used to assume that regs doesn't change - fix automatic address calculation for function arguments when an argument has a spurious DW_OP_piece at entry 2020-07-28 16:19:51 +00:00			`fmt.Printf("%d %d\n", a, b)`
pkg/proc: use DW_AT_decl_line to determine var visibility Fixes #186, #83 2017-09-08 10:31:03 +00:00			`}`