Lines Matching refs:execve

70 on execve in multi-threaded process.
147 ptrace-stop - see "Syscall-stops" and "execve" sections below for
270 signal death, or exit caused by execve in multi-threaded process.
290 or die silently (if execve syscall happened in another thread).
426 	1.x execve under ptrace.
428 During execve, kernel destroys all other threads in the process, and
429 resets execve'ing thread tid to tgid (process id). This looks very
436 (on which tracee - leader? execve-ing one?).
438 The execve-ing tracee changes its pid while it is in execve syscall.
449 tracer), during execve it will appear as if it has become a tracee of
450 the tracer of execve'ing tracee. All these effects are the artifacts of
454 case. It enables PTRACE_EVENT_EXEC stop which occurs before execve
468 Currently, there is no way to retrieve former pid of execve-ing tracee.
470 may be unable to know which tracee  execve-ed and therefore no longer
473 Example: two threads execve at the same time:
476  PID1 execve("/bin/foo", "foo" <unfinished ...>
479  PID2 execve("/bin/bar", "bar" <unfinished ...>
483  PID0 <... execve resumed> )             = 0
485 In this situation there is no way to know which execve succeeded.
487 If PTRACE_O_TRACEEXEC option is NOT in effect for the execve'ing
488 tracee, kernel delivers an extra SIGTRAP to tracee after execve syscall
495 post-execve SIGTRAP signal to the user, and would suppress its delivery
530 exit. As explained above, if one of other threads execve's, thread
531 group leader death will *never* be reported. If execve-ed thread is not
532 traced by this tracer, tracer will never know that execve happened.