I believe this is asking for a single handler that will apply to all
goroutines, to which the answer is no such feature exists
- sean
On Sat, May 28, 2022, 03:09 Ian Lance Taylor <i...@golang.org> wrote:
> On Fri, May 27, 2022 at 10:42 AM Aggarwal Sre <sre.aggar...@gmail.com>
> wrote:
> >
> > Is there a recommended pattern besides adding a defer call ( with
> recover call, to collect debug stack trace) to each goroutine, for
> collecting a stack trace when a golang is crashing due to any sort of panic.
> >
> > In other words, is there a way to register an uber handler ( probably
> using OS signals) at the main function level, to indicate that a golang
> program crashed and stacktrace to clearly specify where exactly?
>
> A panic handle is run at the bottom of the stack. If you write this:
>
> defer func() {
> if recover() != nil {
> fmt.Printf("%s", debug.Stack())
> }
> }()
>
> in your main function, it will print a stack trace showing the point
> of the panic.
>
> Ian
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/CAOyqgcV4d9HxDbdp_in95j6aKFF_m%2BN_hFdeyUMuMOWRt5%2B6dw%40mail.gmail.com
> .
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/CAGabyPoRyv63ztmyrAGkuQ4u8Dcqffo4dUVo6H%3DczLU7%3DvsVcw%40mail.gmail.com.
