gecko-dev/toolkit/crashreporter/breakpad-client
Gabriele Svelto 3e1f486e5c Bug 1724928 - Catch EXC_CRASH exceptions on macOS r=KrisWright
EXC_CRASH exceptions wrap some of the other exceptions under certain
conditions. They are delivered to the exception handler when the wrapped
exception has not been caught by a previous handler. They carry no data
of their own but pack the data of the original exception instead, see:

2ff845c2e0/bsd/kern/kern_exit.c (L1056-L1066)

We match Crashpad behavior to not store these exceptions directly in the
minidump but rather unpack the original exception and store it instead.
Because of that I haven't added functionality to print them out.

Additionally it seems that they can also wrap uncaught signals and deliver
those instead of a mach exception. While extracting the original signal is
a trivial operation I was unable to actually generate one in the first
place. As such I've added no specific functionality to deal with those either.
This also matches crashpad behavior.

Differential Revision: https://phabricator.services.mozilla.com/D123532
2021-08-31 09:18:50 +00:00
..
linux Bug 1725145 - Preparation for the hybrid build env. r=necko-reviewers,firefox-build-system-reviewers,valentin,glandium 2021-08-25 10:46:17 +00:00
mac Bug 1724928 - Catch EXC_CRASH exceptions on macOS r=KrisWright 2021-08-31 09:18:50 +00:00
windows Bug 1541571 - Breakpad threads should have names, r=gsvelto. 2021-02-25 22:42:50 +00:00
minidump_file_writer-inl.h
minidump_file_writer.cc Bug 1660516 - Crash pings sometimes have null bytes after module names. r=gsvelto 2020-10-28 09:56:53 +00:00
minidump_file_writer.h Bug 1660516 - Crash pings sometimes have null bytes after module names. r=gsvelto 2020-10-28 09:56:53 +00:00
minidump_file_writer_unittest.cc
moz.build Bug 1588710 - Do not fail on stack protector on some asm chromium & breakpad sandboxing code r=mhentges 2020-11-27 10:14:01 +00:00