Mark Mentovai 8c70c504b2 Make breakpad_unittests work with Chrome's test runner instead of gtest's ... Chrome's test runner on Linux installs its own StackDumpSignalHandler which swallows signals and doesn't re-raise them. This is sloppy, but apparently there are reasons (https://crbug.com/551681). For breakpad_unittests, it causes problems where a test process expects (via waitpid()) to observe a child crash. Deal with those cases by explicitly restoring the default signal handler. In another case, Chrome's test runner seems to have been arriving at the conclusion that it was to expect output from a child. Transitioning from exit() to _exit() fixes this problem, and it's not necessarily a bad idea to do this in post-fork() children without an execve() anyway. Bug: chromium:949098 Change-Id: I5a6af0c2a09cd8eac9998358f6d5ea665288236f Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/1575670 Reviewed-by: Mark Mentovai <mark@chromium.org>		2019-04-19 21:42:27 +00:00
..
build	Fix MSVC build on 64-bit	2017-09-25 07:10:11 +00:00
client	Make breakpad_unittests work with Chrome's test runner instead of gtest's	2019-04-19 21:42:27 +00:00
common	Make breakpad_unittests work with Chrome's test runner instead of gtest's	2019-04-19 21:42:27 +00:00
google_breakpad	breakpad: Remove semicolons.	2019-02-21 15:43:19 +00:00
processor	Always emit a 32-bit crash address for 32-bit architectures	2019-01-30 16:21:52 +00:00
third_party	List missing 64-bit arches in the bundled curl	2017-11-13 19:50:29 +00:00
tools	Fix dump_syms unit tests on Windows.	2019-03-18 23:08:12 +00:00
breakpad_googletest_includes.h	test: allow use of system gmock/gtest libs	2016-01-25 19:27:56 -05:00
config.h.in	Only use O_CLOEXEC on platforms that support it	2017-05-10 21:32:37 +00:00