{"push_id":722804893,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b3a8b0574ad94c0b26cacb2e926848f18ecb29f3","before":"d5004ee69e117936890bf85b924c38f3bb505a6d","commits":[{"sha":"b3a8b0574ad94c0b26cacb2e926848f18ecb29f3","author":{"email":"993af7099cb24ce1a88d64108ae1e8b0385f2fc0@gmail.com","name":"Elias Naur"},"message":"runtime: abort on fatal errors and panics in c-shared and c-archive modes\n\nThe default behaviour for fatal errors and runtime panics is to dump\nthe goroutine stack traces and exit with code 2. However, when the process is\nowned by foreign code, it is suprising and inappropriate to suddenly exit\nthe whole process, even on fatal errors. Instead, re-use the crash behaviour\nfrom GOTRACEBACK=crash and abort.\n\nThe motivating use case is issue #11382, where an Android crash reporter\nis confused by an exiting process, but I believe the aborting behaviour\nis appropriate for all cases where Go does not own the process.\n\nThe change is simple and contained and will enable reliable crash reporting\nfor Android apps in Go 1.5, but I'll leave it to others to judge whether it\nis too late for Go 1.5.\n\nFixes #11382\n\nChange-Id: I477328e1092f483591c99da1fbb8bc4411911785\nReviewed-on: https://go-review.googlesource.com/12032\nReviewed-by: Ian Lance Taylor <iant@golang.org>\nRun-TryBot: Ian Lance Taylor <iant@golang.org>\nTryBot-Result: Gobot Gobot <gobot@golang.org>","distinct":true,"url":"https://api.github.com/repos/golang/go/commits/b3a8b0574ad94c0b26cacb2e926848f18ecb29f3"}]}