if I enable core dump generation in my shell with *ulimit* and run a
compiled go program (with GOTRACEBACK=crash set) that has some goroutines
in which one of them causes a program crash; how can I inspect the state of
the goroutines with GDB afterwards? If I fire up GDB with the core dump
there are some threads created one which corresponds to the goroutine that
crashed and the others seems to be garbage collection-related. Running
"info goroutines" works but "goroutine x bt" complains with "You can't do
that without a process to debug.".
How can I see the backtrace from goroutines etc. from a core dump?
Example program that I've played around with, panicking at row 28:
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.