|
Crashpad
|
Swallows EXC_CRASH and EXC_CORPSE_NOTIFY exceptions in test child processes.
More...
#include "test/mac/exception_swallower.h"
Classes | |
| class | ExceptionSwallowerThread |
Static Public Member Functions | |
| static void | SwallowExceptions () |
In a test child process, arranges to swallow EXC_CRASH and EXC_CORPSE_NOTIFY exceptions. More... | |
Swallows EXC_CRASH and EXC_CORPSE_NOTIFY exceptions in test child processes.
This class is intended to be used by test code that crashes intentionally.
On macOS, the system’s crash reporter normally saves crash reports for all crashes in test code, by virtue of being set as the EXC_CRASH or EXC_CORPSE_NOTIFY handler. This litters the user’s ~/Library/Logs/DiagnosticReports directory and can be time-consuming. Reports generated for code that crashes intentionally have no value, and many Crashpad tests do crash intentionally.
Instantiate an ExceptionSwallower object in a parent test process (a process where TEST(), TEST_F(), and TEST_P() execute) to create an exception swallower server running on a dedicated thread. A service mapping for this server will be published with the bootstrap server and made available in the CRASHPAD_EXCEPTION_SWALLOWER_SERVICE environment variable. In a child process, call SwallowExceptions() to look up this service and set it as the EXC_CRASH and EXC_CORPSE_NOTIFY handler. When these exceptions are raised in the child process, they’ll be handled by the exception swallower server, which performs no action but reports that exceptions were successfully handled so that the system’s crash reporter, ReportCrash, will not be invoked.
At most one ExceptionSwallower may be instantiated in a process at a time. If CRASHPAD_EXCEPTION_SWALLOWER_SERVICE is already set, ExceptionSwallower leaves it in place and takes no additional action.
Crashpad’s ASSERT_DEATH_CRASH(), EXPECT_DEATH_CRASH(), ASSERT_DEATH_CHECK(), and EXPECT_DEATH_CHECK() macros make use of this class on macOS, as does the Multiprocess test interface.
|
static |
In a test child process, arranges to swallow EXC_CRASH and EXC_CORPSE_NOTIFY exceptions.
This must be called in a test child process. It must not be called from a parent test process directly. Parent test processes are those that execute TEST(), TEST_F(), and TEST_P(). Test child processes execute ASSERT_DEATH_CRASH(), EXPECT_DEATH_CRASH(), ASSERT_DEATH_CHECK(), EXPECT_DEATH_CHECK(), and Multiprocess::RunChild().
It is an error to call this in a test child process without having first instantiated an ExceptionSwallower object in a parent test project. It is also an error to call this in a parent test process.
1.8.18