debug
debug copied to clipboard
golang
[mirror] debugging tools
It's a single-entry closure laid out like `{pc uintptr, x T}`, and the target pc is for wrapper functions named like pkg.T.m-fm or pkg.(*T).m-fm. So, extract the type name pkg.T...
Match the object size when there are multiple candidates for the pointers to structs with the same struct name and same package name. Also, allow `-` in the package path.
Workaround for errors like: ``` panic: weird mapping Exec goroutine 1 [running]: golang.org/x/debug/internal/gocore.(*Process).readSpans(0xc0003322c0, 0xc0003322c0, 0xa58f780, 0xc00e328d20, 0xc00fa6c000, 0x4b, 0x80) /home/bozaro/github/debug/internal/gocore/process.go:316 +0x304e golang.org/x/debug/internal/gocore.(*Process).readHeap(0xc0003322c0) /home/bozaro/github/debug/internal/gocore/process.go:272 +0x77b golang.org/x/debug/internal/gocore.Core(0xc00016e000, 0x40, 0x0, 0x0) /home/bozaro/github/debug/internal/gocore/process.go:157 +0x2c4...
This change ignores files without executable regions to avoid errors on loading debug info from this files. In our case we got confusing `bad magic number` errors on parsing files...
It was parsing `args[0]` but reporting an error on `args[1]`, which might panic and obscure the error. Also do the initial parsing earlier, to save effort reading the core if...
Module ergochat/readline is a fork that is actively maintained and includes numerous bug fixes that are not present in the original module. Additionally, this change reduces the number of indirect...
Ran into the below two nil-ptr exceptions. Culprit seemed to be due to parsing a `runtime.itabTableType` resource: ``` 2 40960 81920 [1+8?]runtime.itabTableType ``` Added two nil-ptr checks to skip if...
