Lines Matching refs:waitpid

8 Ptrace API (ab)uses standard Unix parent/child signaling over waitpid.
40 about this event is delivered through waitpid API similarly to
81 that waitpid(WNOHANG) will reliably report tracee's death status if
82 ptrace operation returned ESRCH. waitpid(WNOHANG) may return 0 instead.
94 waitpid API. Tracer should use waitpid family of syscalls to wait for
97 	pid = waitpid(pid_or_minus_1, &status, __WALL);
109 Setting of WCONTINUED bit in waitpid flags is not recommended: the
113 Use of WNOHANG bit in waitpid flags may cause waitpid return 0 ("no
115 notification. Example: kill(tracee, SIGKILL); waitpid(tracee, &status,
124 SYSEMU_SINGLESTEP]. They all are reported as waitpid result with
144 Signal-delivery-stop is observed by tracer as waitpid returning with
213 Group-stop is observed by tracer as waitpid returning with
230 into another waitpid call.
235 doesn't restart tracee before entering into next waitpid, future
245 PTRACE_EVENT stops are observed by tracer as waitpid returning with
293 waitpid returning with WIFSTOPPED(status) == true, WSTOPSIG(status) ==
439 (Remember, under ptrace 'pid' returned from waitpid, or fed into ptrace
504 Ptrace API (ab)uses standard Unix parent/child signaling over waitpid.
506 kinds of waitpid notifications when child process is traced by some
515 consumes waitpid result, to real parent (to real parent only when the