Thanks for mentioning panicwrap. They've added forwardable signal recently, which I certainly need to be able to exit from the app by sending TERM to the parent process. But I think there some errors in implementation. I mentioned them here https://github.com/mitchellh/panicwrap/commit/ba9e1a65e0f7975f055d50a2c0201c50d941c24c .
On Thursday, December 15, 2016 at 6:12:13 PM UTC+4, mhh...@gmail.com wrote: > > hi, > > https://github.com/mitchellh/panicwrap ? > https://github.com/mitchellh/panicwrap/blob/master/panicwrap.go#L145 > > to go a little further, > https://github.com/mh-cbon/report-panic/blob/master/demo/demo.go#L12 ? > > > > On Thursday, December 15, 2016 at 11:08:34 AM UTC+1, Maksim Sitnikov wrote: >> >> >> On Thursday, December 15, 2016 at 12:23:48 PM UTC+4, Dave Cheney wrote: >>> >>> The stack trace is written to stderr, export GOTRACEBACK=all if you want >>> a stack trace of all goroutines not just the one that faulted. >> >> >> Thanks you. Yes, it is. But how can I send it? App crashes when there is >> a panic in any goroutine. And I can't control creation of all goroutines. >> Is there any solution? >> > -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
