delve/pkg/dwarf/frame
aarzilli 5372588c61 proc: support cgo stacktraces
When creating a stack trace we should switch between the goroutine
stack and the system stack (where cgo code is executed) as appropriate
to reconstruct the logical stacktrace.

Goroutines that are currently executing on the system stack will have
the SystemStack flag set, frames of the goroutine stack will have a
negative FrameOffset (like always) and frames of the system stack will
have a positive FrameOffset (which is actually just the CFA value for
the frame).

Updates #935
2017-11-28 11:00:53 -08:00
..
testdata Move top-level packages into pkg 2017-02-08 12:17:19 -08:00
entries_test.go Move top-level packages into pkg 2017-02-08 12:17:19 -08:00
entries.go proc: refactor stack.go to use DWARF registers 2017-11-17 10:17:24 -08:00
expression_constants.go Move top-level packages into pkg 2017-02-08 12:17:19 -08:00
parser_test.go vendor: update vendored packages (#791) 2017-04-17 14:13:00 -07:00
parser.go pkg/dwarf/frame: fix parsing of zero length entries 2017-11-03 20:57:04 +01:00
table.go proc: support cgo stacktraces 2017-11-28 11:00:53 -08:00