On Tue, Aug 30, 2016 at 6:06 AM, wrote:
>
> From my point of view, a better solution would be, when Go has an option
> (maybe via GOTRACEBACK env var) to trace C threads as well, for example by
> using the cgo traceback functions introduced in Go 1.7.
I don't see how that would work. The Go cod
Hi,
I have a Go executable that uses a shared C library which spawns it own
threads. In case of a crash (in Go or C code), I want to dump all
stacktraces of all C threads and Go routines into a crash dump file. Go
does not handle signals in non-Go threads executing non-Go code, so I have
to in
