Lines Matching full:process
9 .Nd process tracing and debugging
22 It allows one process
25 process)
29 process).
30 The tracing process must first attach to the traced process, and then
33 system calls to control the execution of the process, as well as access
34 process memory and register state.
35 For the duration of the tracing session, the traced process will be
37 with its parent process ID (and resulting behavior)
38 changed to the tracing process.
39 It is permissible for a tracing process to attach to more than one
40 other process at a time.
41 When the tracing process has completed its work, it must detach the
42 traced process; if a tracing process exits without first detaching all
45 Most of the time, the traced process runs normally, but when it
50 The tracing process is expected to notice this via
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
57 traced process behavior, or use of the
61 process,
62 or an event in the traced process.
63 The tracing process may choose to intercept the signal, using it to
64 observe process behavior (such as
66 or forward the signal to the process if appropriate.
72 A traced process may report additional signal stops corresponding to
73 events in the traced process.
79 The tracing process can use the
94 The signal stop for a new child process enabled via
103 Normally, exiting tracing process should wait for all pending
108 If tracing process exits without detaching, for instance due to abnormal
129 For operations affecting the global process state, the process ID
135 target, and system will perform the request on the process owning
137 If a thread operation got the process ID as
140 by the process.
142 process or thread ID as the target.
171 requests from processes that have no groups in common with the target process,
179 process, even if the requesting process' jail is an ancestor of the target
180 process'.
186 process can only be traced with
190 Process can deny attempts to trace itself with
200 Each traced process has a tracing event mask.
201 An event in the traced process only reports a
233 This event flag controls tracing for new child processes of a traced process.
238 The new child process will include the
244 The traced process will report a stop that includes the
247 The process ID of the new child process will also be present in the
251 If the new child process was created via
253 the traced process's stop will also include the
258 they do not inherit the event mask of the traced process.
279 Report a stop event when a parent process resumes after a
282 When a thread in the traced process creates a new child process via
288 occurs just after the child process is created,
289 but before the thread waits for the child process to stop sharing process
291 If a debugger is not tracing the new child process,
292 it must ensure that no breakpoints are enabled in the shared process
293 memory before detaching from the new child process.
294 This means that no breakpoints are enabled in the parent process either.
298 flag enables a new stop that indicates when the new child process stops
299 sharing the process memory of the parent process.
300 A debugger can reinsert breakpoints in the parent process and resume it
307 The default tracing event mask when attaching to a process via
324 calls are made by the tracing process, and the
326 argument specifies the process ID of the traced process
334 This request is the only one used by the traced process; it declares
335 that the process expects to be traced by its parent.
337 (If the parent process does not expect to trace the child, it will
338 probably be rather confused by the results; once the traced process
341 When a process has used this request and calls
362 of data from the traced process's address space.
377 (in the traced process's virtual address space)
393 the traced process's address space.
423 The traced process continues execution.
435 provides a signal number to be delivered to the traced process as it
438 The traced process is single stepped one instruction.
447 provides a signal number to be delivered to the traced process as it
450 The traced process terminates, as if
456 This request allows a process to gain control of an otherwise
457 unrelated process and begin tracing it.
458 It does not need any cooperation from the process to trace.
462 specifies the process ID of the process to trace, and the other
464 This request requires that the target process must have the same real
465 UID as the tracing process, and that it must not be executing a setuid
467 (If the tracing process is running as root, these restrictions do not
469 The tracing process will see the newly-traced process stop and may
474 succeeds, the traced process is no longer traced and continues
477 This request reads the traced process's machine registers into the
488 it loads the traced process's machine registers from the
497 This request reads the traced process's floating-point registers into
509 it loads the traced process's floating-point registers from the
518 This request reads the traced process's debug registers into
530 it loads the traced process's debug registers from the
539 This request reads the registers from the traced process.
553 This request writes to the registers of the traced process.
574 also known as light-weight process, that caused the traced process to stop.
622 registers according to the ABI of the current process, and modify them,
632 program being executed by debuggee process has been changed by successful
643 Indicates that the process is returning from a call to
645 that created a new child process.
646 The process identifier of the new process is available in the
665 Note that this event is not reported when the last LWP in a process exits.
666 The termination of the last thread is reported via a normal process exit
671 that created a new child process.
675 Indicates that the thread has resumed after a child process created via
677 has stopped sharing its address space with the traced process.
683 Note that signals that are delivered to the process would not appear
696 The process identifier of the new child process.
727 traced process.
740 This request will turn on single stepping of the specified process.
743 This request will turn off single stepping of the specified process.
751 event flag to trace all future system call entries and continue the process.
761 event flag to trace all future system call exits and continue the process.
772 the process.
845 This request controls tracing for new child processes of a traced process.
850 is set in the traced process's event tracing mask.
855 is cleared from the traced process's event tracing mask.
862 is set in the traced process's event tracing mask.
867 is cleared from the traced process's event tracing mask.
869 This request reads the traced process's event tracing mask into the
875 This request sets the traced process's event tracing mask from the
882 the traced process as the return value from
884 This provides a low-cost way for the tracing process to determine if the
888 process.
919 The tracing process can then take appropriate action, such as restarting.
971 flag of the process map entry, but device mappings are not dumped even with
985 Request to execute a syscall in the context of the traced process,
1019 The process must be stopped before dumping or initiating a remote system call.
1020 A single thread in the target process is temporarily unsuspended
1029 call returns, and the process must be waited upon using
1062 signal is not sent to a process executing in capability mode,
1068 This might result in the target process deadlock.
1276 which return the value read from the process memory on success.
1298 No process having the specified process ID exists.
1303 A process attempted to use
1326 was attempted on a process with no valid register set.
1332 This can also be caused by changes to the VM map of the process.
1378 was attempted on a process that was already being traced.
1380 A request attempted to manipulate a process that was being traced by
1381 some process other than the one making the request.
1386 specified a process that was not stopped.
1394 attempted to manipulate a process that was not being traced at all.
1398 on a process in violation of the requirements listed under
1418 occurred when accessing process memory.