1 .TH dapptrace 1m "$Date:: 2007-08-05 #$" "USER COMMANDS"
3 dapptrace \- trace user and library function usage. Uses DTrace.
6 [\-acdeFlhoU] [\-u lib] { \-p PID | command }
8 dapptrace prints details on user and library function calls. By
9 default it traces user functions only, options can be used to
10 trace library activity.
12 Of particular interest is the elapsed times and on cpu times, which
13 can identify both function calls that are slow to complete, and those
14 which are consuming CPU cycles.
16 Since this uses DTrace, only the root user or users with the
17 dtrace_kernel privilege can run this command.
21 stable - needs the pid provider.
28 dynamic variable buffer size. Increase this if you notice dynamic
29 variable drop errors. The default is "4m" for 4 megabytes per CPU.
32 print function call counts
35 print relative timestamps, us
38 print elapsed times, us
41 print flow indentation
44 force printing of pid/lwpid per line
47 print on-cpu times, us
53 trace this library instead
56 trace all library and user functions
60 run and examine the "df -h" command,
72 print using flow indents,
78 print elapsed and CPU times,
86 Process ID / Lightweight Process ID
89 relative timestamps to the start of the thread, us (microseconds)
92 elapsed time for this system call, us
95 on-cpu time for this system call, us
98 function call name, with some arguments in hexadecimal
101 See the DTraceToolkit for further documentation under the
102 Docs directory. The DTraceToolkit docs may include full worked
103 examples with verbose descriptions explaining the output.
105 dapptrace will run forever until Ctrl\-C is hit, or if a command was
106 executed dapptrace will finish when the command ends.
111 dappprof(1M), dtrace(1M), apptrace(1)