mirror of
https://github.com/chromium/crashpad.git
synced 2024-12-27 07:14:10 +08:00
1669ca2bac
The design for running all Crashpad unit tests on Chromium’s try- and buildbots involves pulling all tests into a single monolithic crashpad_tests executable. Many Crashpad tests base the name of their child executables or modules on the name of the main test executable. Since the main test executable will have a different name in the in-Chromium build, knowledge of the test executable name (referred to as “module” here) needs to be added to the tests themselves. This introduces TestPaths::BuildArtifact(), which allows the module name to be specified. For Crashpad’s standalone build, the module name is verified against the main test executable’s name. TestPaths::BuildArtifact() can also locate paths in the alternate 32-bit output directory for 64-bit Windows tests, taking on the responsibility for what the new (5e9ed4cb9f69) TestPaths::Output32BitDirectory(), now obsolete, did. Bug: chromium:779790 Change-Id: I64c4a2190b6319e487c999812a7cfc512a75a700 Reviewed-on: https://chromium-review.googlesource.com/747536 Reviewed-by: Scott Graham <scottmg@chromium.org>
Crashpad
Crashpad is a crash-reporting system.
Documentation
- Project status
- Developing Crashpad: instructions for getting the source code, building, testing, and contributing to the project.
- Crashpad interface documentation
- Crashpad tool man pages
- Crashpad overview design
Source Code
Crashpad’s source code is hosted in a Git repository at https://chromium.googlesource.com/crashpad/crashpad.
Other Links
- Bugs can be reported at the Crashpad issue tracker.
- The Crashpad Buildbots perform automated builds and tests.
- crashpad-dev is the Crashpad developers’ mailing list.