, Tamás Gulácsi wrote:
>
> 2016. december 15., csütörtök 13:12:16 UTC+1 időpontban Maksim Sitnikov a
> következőt írta:
>>
>> Justin, Your suggestion seems to be the only viable solution at the
>> moment. Thank you.
>>
>> But if there is anything else, will be
I ended up with this fork https://github.com/bugsnag/panicwrap . It
correctly handles signals from the supervisor.
--
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
tps://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 tra
Justin, Your suggestion seems to be the only viable solution at the moment.
Thank you.
But if there is anything else, will be glad to hear.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving
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
On Thursday, December 15, 2016 at 9:17:09 AM UTC+4, Miki Tebeka wrote:
>
> You can probably add a defer/recover to your main which will "catch"
> panics, report the panic and stack trace and then exit your program with
> non zero code.
>
This won't work. Because it's not possible to recover
Hello,
I have an app with external dependencies (packages). These packages
potentially can start goroutine. And this goroutine can raise (runtime)
panic (poorly written etc.) and crash my app. Of course, my app will be
restarted by service supervisor, but I need to send a report about each
