Man page - trace-cmd-dump(1)
Packages contas this manual
- trace-cmd(1)
- trace-cmd-attach(1)
- tracecmd_buffer_instance_handle(3)
- trace-cmd-clear(1)
- tracecmd_get_first_ts(3)
- trace-cmd-stat(1)
- tracecmd_follow_missed_events(3)
- tracecmd_get_guest_cpumap(3)
- trace-cmd-check-events(1)
- tracecmd_get_tsc2nsec(3)
- trace-cmd.dat.v6(5)
- trace-cmd-convert(1)
- tracecmd_get_cpu_map(3)
- trace-cmd-sqlhist(1)
- tracecmd_get_private(3)
- tracecmd_open(3)
- tracecmd_iterate_events(3)
- tracecmd_set_loglevel(3)
- tracecmd_map_vcpus(3)
- tracecmd_open_fd(3)
- tracecmd_buffer_instances(3)
- trace-cmd-stop(1)
- tracecmd_set_private(3)
- trace-cmd-listen(1)
- trace-cmd.dat.v7(5)
- tracecmd_get_tep(3)
- tracecmd_filter_add(3)
- trace-cmd-extract(1)
- tracecmd_iterate_reset(3)
- tracecmd_map_get_private(3)
- trace-cmd-restore(1)
- trace-cmd-show(1)
- tracecmd_map_find_by_host_pid(3)
- trace-cmd-hist(1)
- tracecmd_get_traceid(3)
- tracecmd_iterate_events_multi(3)
- trace-cmd-mem(1)
- trace-cmd-report(1)
- tracecmd_read_cpu_first(3)
- trace-cmd-reset(1)
- trace-cmd-start(1)
- tracecmd_read_data(3)
- trace-cmd-agent(1)
- trace-cmd-profile(1)
- trace-cmd-dump(1)
- tracecmd_map_set_private(3)
- tracecmd_map_get_guest(3)
- trace-cmd-list(1)
- libtracecmd(3)
- tracecmd_map_get_host_pid(3)
- trace-cmd-stack(1)
- tracecmd_add_ts_offset(3)
- tracecmd_buffer_instance_name(3)
- tracecmd_read_at(3)
- tracecmd_init_data(3)
- tracecmd_open_head(3)
- trace-cmd-split(1)
- tracecmd_follow_event(3)
- trace-cmd-set(1)
- trace-cmd-snapshot(1)
- trace-cmd-stream(1)
- trace-cmd-record(1)
- tracecmd_free_record(3)
- tracecmd_close(3)
- trace-cmd-options(1)
Package: trace-cmd
apt-get install trace-cmd
apt-get install trace-cmd
Manuals in package:
Documentations in package:
Manual
| TRACE-CMD-DUMP(1) | libtracefs Manual | TRACE-CMD-DUMP(1) |
NAME
trace-cmd-dump - show a meta data from a trace file, created by trace-cmd record
SYNOPSIS
trace-cmd dump [OPTIONS] [input-file]
DESCRIPTION
The trace-cmd(1) dump command will display the meta data from a trace file created by trace-cmd record.
OPTIONS
-i input-file
By default, trace-cmd dump will read the file
trace.dat. But the -i option open up the given input-file
instead. Note, the input file may also be specified as the last item on the
command line.
-v, --validate
Check if the input file is a valid trace file, created by
trace-cmd.
--summary
Print a meta data summary - initial format and a short
description of each file section. This is the default action, if no arguments
are specified.
--head-page
Print the header page information, stored in the
file.
--head-event
Print the event header information, stored in the
file.
--ftrace-events
Print formats of ftrace specific events.
--systems
Print information of event systems, stored in the file -
name and number of events for each system.
--events
Print formats of all events, stored in the file.
--kallsyms
Print information of the mapping of function addresses to
the function names.
--printk
Print trace_printk() format strings, stored in the
file.
--cmd-lines
Print mapping a PID to a process name.
--options
Print all options, stored in the file.
--flyrecord
Print the offset and the size of tracing data per each
CPU.
--clock
Print the trace clock, used for timestamp of the tracing
events, stored in the file.
--all
Print all meta data from the file.
--help
Print usage information.
--verbose[=level]
Set the log level. Supported log levels are
"none", "critical", "error",
"warning", "info", "debug", "all" or
their identifiers "0", "1", "2", "3",
"4", "5", "6". Setting the log level to specific
value enables all logs from that and all previous levels. The level will
default to "info" if one is not specified.
Example: enable all critical, error and warning logs
trace-cmd report --verbose=warning
EXAMPLES
# trace-cmd dump --summary -i trace.dat
Tracing meta data in file trace.dat:
[Initial format]
6 [Version]
0 [Little endian]
8 [Bytes in a long]
4096 [Page size, bytes]
[Header info, 205 bytes]
[Header event, 205 bytes]
[Ftrace format, 15 events]
[Events format, 2 systems]
[Kallsyms, 7144493 bytes]
[Trace printk, 2131 bytes]
[Saved command lines, 117 bytes]
8 [CPUs with tracing data]
[12 options]
[Flyrecord tracing data]
# trace-cmd dump --flyrecord -i trace.dat
[Flyrecord tracing data]
7176192 0 [offset, size of cpu 0]
7176192 0 [offset, size of cpu 1]
7176192 0 [offset, size of cpu 2]
7176192 4096 [offset, size of cpu 3]
7180288 4096 [offset, size of cpu 4]
7184384 0 [offset, size of cpu 5]
7184384 0 [offset, size of cpu 6]
7184384 0 [offset, size of cpu 7]
# trace-cmd dump --summary --systems -i trace.dat
Tracing meta data in file trace.dat:
[Initial format]
6 [Version]
0 [Little endian]
8 [Bytes in a long]
4096 [Page size, bytes]
[Header info, 205 bytes]
[Header event, 205 bytes]
[Ftrace format, 15 events]
[Events format, 3 systems]
sched 23 [system, events]
irq 5 [system, events]
kvm 70 [system, events]
[Kallsyms, 7144493 bytes]
[Trace printk, 2131 bytes]
[Saved command lines, 157 bytes]
8 [CPUs with tracing data]
[11 options]
[Flyrecord tracing data]
# trace-cmd dump --summary --systems -i trace.dat File trace.dat is a valid trace-cmd file
SEE ALSO
trace-cmd(1), trace-cmd.dat(1)
AUTHOR
Steven Rostedt <rostedt@goodmis.org[1]>, author of trace-cmd. Tzvetomir Stoyanov <tz.stoyanov@gmail.com[2]>, author of this man page.
RESOURCES
https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
COPYING
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
NOTES
- 1.
- rostedt@goodmis.org
mailto:rostedt@goodmis.org
- 2.
- tz.stoyanov@gmail.com
mailto:tz.stoyanov@gmail.com
| 01/07/2025 | libtracefs |