-
Notifications
You must be signed in to change notification settings - Fork 74
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ensure that the Centipede runner writes the failure atomically and on…
…ly once. The atomicity is needed because the function `WriteFailureDescription()` may be called from multiple threads: from the main thread, e.g. for a GoogleTest assertion failure, and from the watchdog thread, e.g. for an OOM. The function should write the failure only once because for failures like stack overflow, it gets called twice: the first time for the stack overflow itself, and the second time from the SIGABRT handler handling the abort that follows the detected stack overflow. PiperOrigin-RevId: 695434225
- Loading branch information
1 parent
63b0966
commit f0969ce
Showing
3 changed files
with
48 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters