Lines Matching refs:delivery

29 be further subdivided into signal-delivery-stop, group-stop,
43 Note that killing signal will first cause signal-delivery-stop (on one
48 SIGKILL operates similarly, with exceptions. No signal-delivery-stop is
122 The following kinds of ptrace-stops exist: signal-delivery-stops,
131 	1.x.x Signal-delivery-stop
136 thread is traced, it enters signal-delivery-stop. By this point, signal
139 the next ptrace request. This second step of signal delivery is called
141 signal-delivery-stop doesn't happen until signal is unblocked, with the
144 Signal-delivery-stop is observed by tracer as waitpid returning with
154 After signal-delivery-stop is observed by tracer, tracer should restart
162 distinguish it from signal-delivery-stop.
178 signal-delivery-stop, restarts tracee with ptrace(PTRACE_rest, pid, 0,
184 signal-delivery-stop. Tracer can't suppress this side-effect (it can
187 waking up from group-stop may be followed by signal-delivery-stop for
207 Note that stopping signal will first cause signal-delivery-stop (on one
285 signal-delivery-stop never happens between syscall-enter-stop and
297 Syscall-stops can be distinguished from signal-delivery-stop with
367 SYSEMU_SINGLESTEP. If tracee is in signal-delivery-stop, sig is the
377 see tracee enter signal-delivery-stop with other signal(s) first! The
392 signal-delivery-stop.
399 signal-delivery-stop after they exit syscall which created them.
403 to be in ptrace-stop. If tracee is in signal-delivery-stop, signal can
408 thread), wait for tracee to stop in signal-delivery-stop for SIGSTOP
414 delivery happens while it is - not even SIGSTOP.
423 signal-delivery-stop, pending signal is injected.
495 post-execve SIGTRAP signal to the user, and would suppress its delivery