|ktrace(1)||enable kernel process tracing|
|ktrace, ktrgenio, ktrnamei, KTRPOINT, ktrpsig, ktrsyscall, ktrsysret(9)||process tracing kernel interface|
|KTRACE(1)||General Commands Manual||KTRACE(1)|
ktraceenables kernel trace logging for the specified processes. By default, kernel trace data is logged to the file ktrace.out, unless overridden by the
-foption. The kernel operations traced are system calls, namei translations, signal processing and I/O.
Once tracing is enabled on a process, trace data will be logged until either the process exits or the trace point is cleared. A traced process can generate enormous amounts of log data quickly; it is strongly suggested that users memorize how to disable tracing before attempting to trace a process. The following command is sufficient to disable tracing on all user owned processes and, if executed by root, all processes:
$ ktrace -C
The trace file is not human-readable; use kdump(1) to decode it.
The options are as follows:
LD_BIND_NOWenvironment variable to specify that the dynamic linker should process relocations immediately instead of as they are encountered. This eliminates the resulting ld.so(1) relocation sequences.
-gflag is permitted).
-pflag is permitted).
Xare enabled. The following table equates the letters with the trace points:
command options are mutually exclusive.
$ ktrace -p 34
Trace all kernel operations of processes in process group 15 and pass the trace flags to all current and future children:
$ ktrace -idg 15
Disable all tracing of process 65:
$ ktrace -cp 65
Disable tracing signals on process 70 and all current children:
$ ktrace -t s -cdp 70
Enable tracing of I/O on process 67:
$ ktrace -ti -p 67
Run the command w(1), tracing only system calls:
$ ktrace -tc w
Disable all tracing to the file "tracedata":
$ ktrace -c -f tracedata
Disable tracing of all processes owned by the user:
$ ktrace -C
ktracecommand appeared in 4.4BSD.
|July 18, 2016||OpenBSD-current|