gecko-dev/toolkit/components/crashes
Gabriele Svelto 43c10532d4 Bug 1353168 - Add a crash annotation to distinguish between web, file and extension content processes; r=bsmedberg
This adds the RemoteType annotation to a content crash report so that we can
distinguish between content processes that crashed while running remote, local
or extension code. The annotation is passed along the others to Socorro by the
crashreporter and is also whitelisted for inclusion in the crash ping.

MozReview-Commit-ID: 4avo0IWfMGf

--HG--
extra : rebase_source : 8d03f7e166b5762a5ce7cab13c2101302b4f1d2f
2017-06-01 11:16:11 +02:00
..
docs Bug 1293656 - Store all crash annotations in the crash manager's database and filter out privacy-sensitive ones when sending a crash ping r=bsmedberg 2016-10-19 12:48:19 +02:00
tests/xpcshell Bug 1353168 - Add a crash annotation to distinguish between web, file and extension content processes; r=bsmedberg 2017-06-01 11:16:11 +02:00
CrashManager.jsm Bug 1353168 - Add a crash annotation to distinguish between web, file and extension content processes; r=bsmedberg 2017-06-01 11:16:11 +02:00
CrashManagerTest.jsm Bug 1359326 - Run the minidump analyzer directly from the CrashService code; r=bsmedberg 2017-05-11 14:03:50 +02:00
CrashService.js Bug 1359326 - Run the minidump analyzer directly from the CrashService code; r=bsmedberg 2017-05-11 14:03:50 +02:00
CrashService.manifest
moz.build Bug 1361417 - Update moz.build crash reporter bug components r=bsmedberg 2017-05-02 09:44:42 -07:00
nsICrashService.idl Bug 1359326 - Run the minidump analyzer directly from the CrashService code; r=bsmedberg 2017-05-11 14:03:50 +02:00