Home | History | Annotate | Download | only in src

Lines Matching full:child

79     "Indicates how to run a death test in a forked child process: "
80 "\"threadsafe\" (child process re-executes the test binary "
82 "\"fast\" (child process runs the death test immediately "
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
358 // True if the death test child process has been successfully spawned.
360 // The exit status of the child process.
376 // implementation uses pipes for child-to-parent communication. But due to
381 // 2. The parent starts the child and provides it with the information
383 // 3. The child acquires the write end of the pipe and signals the parent
387 // 0 and it is destroyed, preventing the child from acquiring it. The
389 // the pipe will not return when the child terminates.
390 // 5. The parent reads child's output through the pipe (outcome code and
415 // Handle to the read end of the pipe to the child process.
416 // The child keeps its write end of the pipe in the status_handle_
419 // Handle to the write end of the pipe to the child process.
421 // Child process handle.
423 // Event the child process uses to signal the parent that it has
426 // ReadFile() calls return when the child terminates.
430 // Waits for the child in a death test to exit, returning its exit
431 // status, or 0 if no child process exists. As a side effect, sets the
440 // Wait until the child either signals that it has acquired the write end
454 // The child has acquired the write end of the pipe or exited.
462 // after the child process has exited.
487 Message() << "Death test child process reported "
493 Message() << "Read from death test child process failed: "
498 // Waits for the child process to exit if it haven't already. This
499 // returns immediately if the child has already exited, regardless of
517 // from the child process only.
537 // The write handle will be closed when the child terminates in _exit().
541 // The AssumeRole process for a Windows death test. It creates a child
543 // death test. The child process is given the --gtest_filter and
606 // Flush the log buffers since the log streams are shared with the child.
609 // The child process will share the standard handles with the parent.
623 TRUE, // Child inherits all inheritable handles (for write_handle_).
653 // PID of child process during death test; 0 in the child process itself.
656 int read_fd_; // Always -1 in the child process.
670 // message from the death test child process and log it with the FATAL
731 // Waits for the child in a death test to exit, returning its exit
732 // status, or 0 if no child process exists. As a side effect, sets the
741 // the child process has exited.
764 Message() << "Death test child process reported unexpected "
771 Message() << "Read from death test child process failed: "
790 // status: The exit status of the child process. On *nix, it is in the
854 // Should be called only in a death test child process.
855 // Writes a status byte to the child's status file descriptor, then
869 // in the child process.
892 // the file descriptors in the child process doesn't throw off the
905 // Redirects all logging to stderr in the child process to prevent
907 // process and append the child process' output to a log.
966 // A struct that encompasses the arguments to the child process of a
969 char* const* argv; // Command-line arguments for the child's call to exec
989 // The main function for a threadsafe-style death test child process.
1093 // it be closed when the child process does an exec:
1202 // handle. This function is called in the child process only.
1223 // process. To obtain one accessible within the child, we need to use