Lines Matching +full:signal +full:- +full:id

36 .Dq re-parented ,
37 with its parent process ID (and resulting behavior)
46 receives a signal
54 signal, examine the state of the stopped process, and cause it to
56 The signal may be a normal process signal, generated as a result of
63 The tracing process may choose to intercept the signal, using it to
66 or forward the signal to the process if appropriate.
72 A traced process may report additional signal stops corresponding to
74 These additional signal stops are reported as
85 signal.
86 Note that multiple events may be associated with a single signal.
94 The signal stop for a new child process enabled via
98 signal.
99 All other additional signal stops use
117 Traced processes are un-stopped if needed, and then continue the execution
129 For operations affecting the global process state, the process ID
131 Similarly, for operations affecting only a thread, the thread ID
134 Still, for global operations, the ID of any thread can be used as the
137 If a thread operation got the process ID as
141 For single-threaded processes there is no difference between specifying
142 process or thread ID as the target.
150 .Bl -tag -width security.bsd.unprivileged_proc_debug
202 signal stop if the corresponding flag is set in the tracing event mask.
204 .Bl -tag -width "Dv PTRACE_SYSCALL"
247 The process ID of the new child process will also be present in the
326 argument specifies the process ID of the traced process
327 or a corresponding thread ID.
332 .Bl -tag -width "Dv PT_GET_EVENT_MASK"
399 .Bd -literal
435 provides a signal number to be delivered to the traced process as it
436 resumes execution, or 0 if no signal is to be sent.
447 provides a signal number to be delivered to the traced process as it
448 resumes execution, or 0 if no signal is to be sent.
454 given as the signal to be delivered.
462 specifies the process ID of the process to trace, and the other
469 The tracing process will see the newly-traced process stop and may
497 This request reads the traced process's floating-point registers into
509 it loads the traced process's floating-point registers from the
574 also known as light-weight process, that caused the traced process to stop.
580 .Bd -literal
603 .Bl -tag -width indent -compact
605 LWP id of the thread
609 .Bl -tag -width "Dv PL_EVENT_SIGNAL" -compact
613 Thread stopped due to the pending signal
618 .Bl -tag -width indent -compact
626 The debugger may examine system call return values in the ABI-defined registers
680 The current signal mask of the LWP
686 The siginfo that accompanies the signal pending.
704 The ABI-specific identifier of the current system call.
810 .Bd -literal
833 .Bl -tag -width EJUSTRETURN -compact
848 is non-zero,
860 is non-zero,
884 This provides a low-cost way for the tracing process to determine if the
894 .Bd -literal
922 to a non-zero value on entry, the pathname of the backing object is returned
949 .Bd -literal
957 .Bl -tag -width pc_flags
964 .Bl -tag -width PC_COMPRESS
968 Include non-dumpable entries into the dump.
997 .Bd -literal
1047 user mode (basically, a signal handler call place).
1062 signal is not sent to a process executing in capability mode,
1070 .Sh ARM MACHINE-SPECIFIC REQUESTS
1071 .Bl -tag -width "Dv PT_SETVFPREGS"
1091 .Sh x86 MACHINE-SPECIFIC REQUESTS
1092 .Bl -tag -width "Dv PT_GETXSTATE_INFO"
1097 The buffer has the same layout as the 32-bit save buffer for the
1101 This request is only valid for i386 programs, both on native 32-bit
1103 For 64-bit amd64 programs, the XMM state is reported as part of
1115 The buffer has the same layout as the 32-bit load buffer for the
1136 .Bd -literal
1225 .Sh PowerPC MACHINE-SPECIFIC REQUESTS
1226 .Bl -tag -width "Dv PT_SETVRREGS"
1248 registers VSR0-VSR31 in the buffer pointed to by
1257 registers VSR0-VSR31 from the buffer pointed to by
1265 Additionally, other machine-specific requests can exist.
1267 Most requests return 0 on success and \-1 on error.
1271 \-1
1272 as a non-error value, among them are
1294 .Bl -tag -width Er
1296 .Bl -bullet -compact
1298 No process having the specified process ID exists.
1301 .Bl -bullet -compact
1312 The signal number
1317 was neither 0 nor a legal signal number.
1344 provided to the x86-specific
1351 provided to the x86-specific
1357 provided to the x86-specific
1367 The base value, provided to the amd64-specific requests
1372 This error will not occur in 32-bit programs.
1375 .Bl -bullet -compact
1389 .Bl -bullet -compact
1403 .Bl -bullet -compact
1410 .Bl -bullet -compact
1421 .Bl -bullet -compact