Lines Matching refs:death
32 // This file implements death tests.
34 #include <gtest/gtest-death-test.h>
73 // The default death test style.
79 "Indicates how to run a death test in a forked child process: "
81 "from the beginning, running only the specific death test) or "
82 "\"fast\" (child process runs the death test immediately "
88 "Instructs to use fork()/_exit() instead of clone() in death tests. "
101 "the single death test to run, and a file descriptor to "
105 "death test. FOR INTERNAL USE ONLY.");
136 // Utilities needed for death tests.
166 // Generates a textual failure message when a death test finds more than
172 msg << "Death tests use fork(), which is unsafe particularly"
182 // Flag characters for reporting a death test that did not die.
187 // An enumeration describing all of the possible ways that a death test
196 // exec-style death test child process, in which case the error
202 // death test child process, which operates on a very small stack. Use
255 // This is called from a death test parent process to read a failure
256 // message from the death test child process and log it with the FATAL
275 GTEST_LOG_(FATAL) << "Error while reading death test internal: "
280 // Death test constructor. Increments the running death test count
285 DeathTestAbort("Cannot run a death test outside of a TEST or "
290 // Creates and returns a death test by dispatching to the current
291 // death test factory.
308 // Provides cross platform implementation for some death functionality.
339 // Called in the parent process only. Reads the result code of the death
352 // True if the death test child process has been successfully spawned.
356 // How the death test concluded.
368 // Called in the parent process only. Reads the result code of the death
377 // failure of the death test) or until the pipe is closed (signifying
398 GTEST_LOG_(FATAL) << "Death test child process reported "
403 GTEST_LOG_(FATAL) << "Read from death test child process failed: "
410 // Signals that the death test code which should have exited, didn't.
411 // Should be called only in a death test child process.
415 // The parent process considers the death test to be a failure if
425 // Assesses the success or failure of a death test, using both private
429 // outcome: An enumeration describing how the death test
430 // concluded: DIED, LIVED, or RETURNED. The death test fails
437 // the test's captured standard error output; the death test
442 // this particular death test, which fails if it is false
446 // reported. Also sets the last death test message string.
456 buffer << "Death test: " << statement() << "\n";
492 // WindowsDeathTest implements death tests on Windows. Due to the
493 // specifics of starting new processes on Windows, death tests there are
533 // The name of the file in which the death test is located.
535 // The line number on which the death test is located.
548 // Waits for the child in a death test to exit, returning its exit
591 // The AssumeRole process for a Windows death test. It creates a child
593 // death test. The child process is given the --gtest_filter and
595 // current death test only.
611 // a death test.
703 // PID of child process during death test; 0 in the child process itself.
712 // Waits for the child in a death test to exit, returning its exit
727 // A concrete death test class that forks, then immediately runs the test
736 // The AssumeRole process for a fork-and-run death test. It implements a
754 // there are multiple threads running before the death test, and another
769 // down in death test subprocesses.
780 // A concrete death test class that forks and re-executes the main
782 // only this specific death test to be run.
790 // The name of the file in which the death test is located.
792 // The line number on which the death test is located.
829 // threadsafe-style death test process.
849 // The main function for a threadsafe-style death test child process.
897 // A threadsafe implementation of fork(2) for threadsafe-style death tests
934 // The AssumeRole process for a fork-and-exec death test. It re-executes the
937 // death test to be re-run.
1003 "Death test count (%d) somehow exceeded expected maximum (%d)",
1029 "Unknown death test style \"%s\" encountered",
