Lines Matching refs:stopped

21 After attachment, each tracee can be in two states: running or stopped.
23 There are many kinds of states when tracee is stopped, and in ptrace
27 In this document, any stopped state in which tracee is ready to accept
72 Tracer cannot assume that ptrace-stopped tracee exists. There are many
73 scenarios when tracee may die while stopped (such as SIGKILL).
76 exists but is not ptrace-stopped (for commands which require stopped
78 Tracer needs to keep track of stopped/running state, and interpret
99 Ptrace-stopped tracees are reported as returns with pid > 0 and
183 group-stopped process. This side effect happens before
234 effectively ignored: tracee doesn't remain stopped, it runs. If tracer
341 using informational commands. They leave tracee in ptrace-stopped state:
361 Another group of commands makes ptrace-stopped tracee run. They have
382 ??? Describe how to attach to a thread which is already group-stopped.
413 be sure that tracee is not already ptrace-stopped, because no signal
416 ??? Describe how to detach from a group-stopped tracee so that it
421 currently buggy, but "as planned" behavior is to leave tracee stopped