trace-cmd-dump(1)

1TRACE-CMD-DUMP(1)              libtracefs Manual             TRACE-CMD-DUMP(1)
2
3
4

NAME

6       trace-cmd-dump - show a meta data from a trace file, created by
7       trace-cmd record
8

SYNOPSIS

10       trace-cmd dump [OPTIONS] [input-file]
11

DESCRIPTION

13       The trace-cmd(1) dump command will display the meta data from a trace
14       file created by trace-cmd record.
15

OPTIONS

17       -i input-file
18           By default, trace-cmd dump will read the file trace.dat. But the -i
19           option open up the given input-file instead. Note, the input file
20           may also be specified as the last item on the command line.
21
22       -v, --validate
23           Check if the input file is a valid trace file, created by
24           trace-cmd.
25
26       --summary
27           Print a meta data summary - initial format and a short description
28           of each file section. This is the default action, if no arguments
29           are specified.
30
31       --head-page
32           Print the header page information, stored in the file.
33
34       --head-event
35           Print the event header information, stored in the file.
36
37       --ftrace-events
38           Print formats of ftrace specific events.
39
40       --systems
41           Print information of event systems, stored in the file - name and
42           number of events for each system.
43
44       --events
45           Print formats of all events, stored in the file.
46
47       --kallsyms
48           Print information of the mapping of function addresses to the
49           function names.
50
51       --printk
52           Print trace_printk() format strings, stored in the file.
53
54       --cmd-lines
55           Print mapping a PID to a process name.
56
57       --options
58           Print all options, stored in the file.
59
60       --flyrecord
61           Print the offset and the size of tracing data per each CPU.
62
63       --clock
64           Print the trace clock, used for timestamp of the tracing events,
65           stored in the file.
66
67       --all
68           Print all meta data from the file.
69
70       --help
71           Print usage information.
72
73       --verbose[=level]
74           Set the log level. Supported log levels are "none", "critical",
75           "error", "warning", "info", "debug", "all" or their identifiers
76           "0", "1", "2", "3", "4", "5", "6". Setting the log level to
77           specific value enables all logs from that and all previous levels.
78           The level will default to "info" if one is not specified.
79
80               Example: enable all critical, error and warning logs
81
82               trace-cmd report --verbose=warning
83

EXAMPLES

85           # trace-cmd dump --summary -i trace.dat
86
87            Tracing meta data in file trace.dat:
88                   [Initial format]
89                           6       [Version]
90                           0       [Little endian]
91                           8       [Bytes in a long]
92                           4096    [Page size, bytes]
93                   [Header info, 205 bytes]
94                   [Header event, 205 bytes]
95                   [Ftrace format, 15 events]
96                   [Events format, 2 systems]
97                   [Kallsyms, 7144493 bytes]
98                   [Trace printk, 2131 bytes]
99                   [Saved command lines, 117 bytes]
100                   8 [CPUs with tracing data]
101                   [12 options]
102                   [Flyrecord tracing data]
103
104           # trace-cmd dump --flyrecord -i trace.dat
105                   [Flyrecord tracing data]
106                            7176192 0      [offset, size of cpu 0]
107                            7176192 0      [offset, size of cpu 1]
108                            7176192 0      [offset, size of cpu 2]
109                            7176192 4096   [offset, size of cpu 3]
110                            7180288 4096   [offset, size of cpu 4]
111                            7184384 0      [offset, size of cpu 5]
112                            7184384 0      [offset, size of cpu 6]
113                            7184384 0      [offset, size of cpu 7]
114
115           # trace-cmd dump --summary --systems -i trace.dat
116
117            Tracing meta data in file trace.dat:
118                   [Initial format]
119                           6       [Version]
120                           0       [Little endian]
121                           8       [Bytes in a long]
122                           4096    [Page size, bytes]
123                   [Header info, 205 bytes]
124                   [Header event, 205 bytes]
125                   [Ftrace format, 15 events]
126                   [Events format, 3 systems]
127                           sched 23 [system, events]
128                           irq 5 [system, events]
129                           kvm 70 [system, events]
130                   [Kallsyms, 7144493 bytes]
131                   [Trace printk, 2131 bytes]
132                   [Saved command lines, 157 bytes]
133                   8 [CPUs with tracing data]
134                   [11 options]
135                   [Flyrecord tracing data]
136
137           # trace-cmd dump --summary --systems -i trace.dat
138           File trace.dat is a valid trace-cmd file
139

AUTHOR

144       Steven Rostedt <rostedt@goodmis.org[1]>, author of trace-cmd. Tzvetomir
145       Stoyanov <tz.stoyanov@gmail.com[2]>, author of this man page.
146

RESOURCES

148       https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
149

COPYING

151       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
152       under the terms of the GNU Public License (GPL).
153

NOTES

155        1. rostedt@goodmis.org
156           mailto:rostedt@goodmis.org
157
158        2. tz.stoyanov@gmail.com
159           mailto:tz.stoyanov@gmail.com
160
161
162
163libtracefs                        10/11/2022                 TRACE-CMD-DUMP(1)