Hi , 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? Thanks in advance, Regards, Vivek Aggarwal -- 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/CABsnPPKPx3fcWwGdCJOv_4JFV-xAjuMCOBxPvFo_GmnRLdekuA%40mail.gmail.com.
