ktracedump.1m (2010 09)

k
ktracedump(1M) ktracedump(1M)
or variable name that arg0 represents if possible. If unable to determine a name, SymArg0
will show arg0 numerically.
SymArg1 Symbolic Argument 1 is a symbolic translation of arg1.
SymArg2 Symbolic Argument 2 is a symbolic translation of arg2.
SymArg3 Symbolic Argument 3 is a symbolic translation of arg3.
Limitations
As described in the LIMITATIONS section of the ktracer (1M) manpage, not all functions are traceable. If
a function is not traceable, calls to it will not be traced, and no trace records will exist with that untrace-
able function as the Function callee in the
ktracedump report. If an untraceable function is reported as
the function Caller , that is because the untraceable function made a procedure call to a traceable func-
tion callee.
# ktracedump -DNF will report the list of functions selected to trace. Only traceable functions can be
added to the list, never untraceable ones.
Traces are generated each time an installed function is executed. If a function of interest is on the traced
function list, but no trace records exist for it, then one of three possibilities has occurred:
1. The function was not executed while
ktracer was active.
2. The circular buffers wrapped around after the function was executed.
3. The function call was inlined by the optimizer.
To eliminate the case of the circular buffers being overwritten, you can do either or both of the following
actions:
1. Configure more traces per CPU (
ktracer -A numtraces).
2. Generate less traces.
To generate less traces, you can try a combinations of these steps:
1. Reduce the list of functions to trace:
a. Remove the 10 most frequently traced functions:
# ktracer -r 10 -B
b. Trace only the named module(s) and function(s):
# ktracer -z -m nfs -a my_func2 -B
2. Shorten the duration that ktracer is active.
3. Trace only one process at a time:
# ktracer -p pid
Information from
ktracedump and /dev/kmem is inherently nonportable.
RETURN VALUE
ktracedump returns 0 upon successful completion and returns non-zero otherwise.
ERRORS
If
ktracedump fails, it returns one of the following errors:
[EPERM] Must be superuser or have SAFER PRIV_DEVOPS privilege.
[EINVAL] Invalid parameters
[ENOSPC] Not enough file system space to save output file.
EXAMPLES
Trace all functions.
# ktracer -R (Turn on tracing of everything possible)
# workload (Run the workload to be traced)
# ktracer -h (Halt tracing)
# ktracedump -D > ktrc.out (Produce basic trace report)
8 Hewlett-Packard Company − 8 − HP-UX 11i Version 3: September 2010