Lines Matching +full:system +full:- +full:trace
1 .TH trace 8 "2016-02-18" "USER COMMANDS"
3 trace \- Trace a function and print its arguments or return value, optionally evaluating a filter. …
5 .B trace [-h] [-b BUFFER_PAGES] [-p PID] [-L TID] [--uid UID] [-v] [-Z STRING_SIZE] [-S] [-M MAX_EV…
6 … [-u] [-T] [-C] [-c CGROUP_PATH] [-n NAME] [-f MSG_FILTER] [-B] [-s SYM_FILE_LIST] [-K] [-U] [-a]
7 [-I header] [-A]
11 trace probes functions you specify and displays trace messages if a particular
20 \-h
23 \-p PID
24 Trace only functions in the process PID.
26 \-L TID
27 Trace only functions in the thread TID.
29 \--uid UID
30 Trace only functions from user UID.
32 \-v
35 \-z STRING_SIZE
39 \-s SYM_FILE_LIST
40 When collecting stack trace in build id format, use the comma separated list for
43 \-S
44 If set, trace messages from trace's own process. By default, this is off to
45 avoid tracing storms -- for example, if you trace the write system call, and
46 consider that trace is writing to the standard output.
48 \-M MAX_EVENTS
49 Print up to MAX_EVENTS trace messages and then exit.
51 \-t
52 Print times relative to the beginning of the trace (offsets), in seconds.
54 \-u
55 Print UNIX timestamps instead of offsets from trace beginning, requires -t.
57 \-T
60 \-C
63 \-c CGROUP_PATH
64 Trace only functions in processes under CGROUP_PATH hierarchy.
66 \-n NAME
69 \-f MSG_FILTER
72 \-B
75 \-K
78 \-U
81 \-a
84 \-I header
89 \-A
90 Print aggregated amount of each trace. This should be used with -M/--max-events together.
103 Probe type \- "p" for function entry, "r" for function return, "t" for kernel
138 the trace message will be printed. The filter can use any valid C expression
142 expression ((int)arg1 < 0) to trace only invocations where arg1 is negative.
143 Note that only arg1-arg6 are supported, and only if the function is using the
148 The predicate expression may also use the STRCMP pseudo-function to compare
155 A printf-style format string that will be used for the trace message. You can
157 %x, %llx -- with the same semantics as printf's. Make sure to pass the exact
164 a symbol). trace will resolve %K specifiers to a kernel symbol, such as
165 vfs__read, and will resolve %U specifiers to a user-space symbol in that
170 block:block_rq_complete tracepoint can print or filter by args->nr_sector. To
182 Trace all invocations of the open system call with the name of the file (from userspace) being open…
184 .B trace '::do_sys_open """%s"", arg2@user'
186 Trace all invocations of the read system call where the number of bytes requested is greater than 2…
188 .B trace '::sys_read (arg3 > 20000) """read %d bytes"", arg3'
190 Trace all malloc calls and print the size of the requested allocation:
192 .B trace ':c:malloc """size = %d"", arg1'
194 Trace returns from the readline function in bash and print the return value as a string:
196 .B trace 'r:bash:readline """%s"", retval'
198 Trace the block:block_rq_complete tracepoint and print the number of sectors completed:
200 .B trace 't:block:block_rq_complete """%d sectors"", args->nr_sector'
202 Trace the pthread_create USDT probe from the pthread library and print the address of the thread's …
204 .B trace 'u:pthread:pthread_create """start addr = %llx"", arg3'
206 Trace the nanosleep system call and print the sleep duration in nanoseconds:
208 .B trace 'p::SyS_nanosleep(struct timespec *ts) "sleep for %lld ns", ts->tv_nsec'
210 Trace the inet_pton system call using build id mechanism and print the stack
212 .B trace -s /lib/x86_64-linux-gnu/libc.so.6,/bin/ping 'p:c:inet_pton' -U
223 Unstable - in development.