{"push_id":837672374,"size":1,"distinct_size":1,"ref":"refs/heads/crash-hook","head":"a5b27bdbb164e6a14c6266cf3082c985d01dfb89","before":"16151a55ae5935ae68cf6ad1aeb79b94ecc4683d","commits":[{"sha":"a5b27bdbb164e6a14c6266cf3082c985d01dfb89","author":{"email":"68841e62bd2061843a4f4a0261e80b673d56389c@google.com","name":"Aaron Jacobs"},"message":"runtime: add a hook for intercepting panic output\n\nThis is \"panic\" in the sense of the word used internally, not just the\nlanguage built-in panic(). So for example it also includes unhandled\nsignals.\n\nThe interested caller can register a function to be called with print()\noutput when a panic is active. When the panic or signal handler is about\nto cause the program to exit, a second function is invoked.\n\nThis allows for custom crash reporting handlers to be written. For\nexample, information about the panic like stack traces can be scraped\nand sent off to a server that presents a UI for looking at aggregated\ncrash information.\n\nChange-Id: Ie57b88dfb5469026647e29b615b585af44d07707","distinct":true,"url":"https://api.github.com/repos/jacobsa/go/commits/a5b27bdbb164e6a14c6266cf3082c985d01dfb89"}]}