1LTTNG-CRASH(1) LTTng Manual LTTNG-CRASH(1)
2
3
4
6 lttng-crash - Recover and view LTTng 2 trace buffers in the event of a
7 crash
8
10 lttng-crash [--extract=PATH | --viewer=VIEWER] [-v | -vv | -vvv] SHMDIR
11
13 The Linux Trace Toolkit: next generation <https://lttng.org/> is an
14 open source software package used for correlated tracing of the Linux
15 kernel, user applications, and user libraries.
16
17 LTTng consists of Linux kernel modules (for Linux kernel tracing) and
18 dynamically loaded libraries (for user application and library
19 tracing).
20
21 The lttng-crash command-line tool is used to recover and view LTTng
22 trace buffers in the event of a system crash.
23
24 lttng-crash reads files within the directory SHMDIR and does one of:
25
26 Without the --extract option
27 Launches a trace reader (see the --viewer option) to view the
28 recovered traces.
29
30 With the --extract option
31 Extracts them as uncorrupted LTTng traces on the file system.
32
33 SHMDIR is the directory specified as the argument of the --shm-path
34 option of the lttng-create(1) command used to create the tracing
35 session for which to recover the traces.
36
38 -x PATH, --extract=PATH
39 Extract recovered traces to path PATH; do not execute the trace
40 viewer.
41
42 -v, --verbose
43 Increase verbosity.
44
45 Three levels of verbosity are available, which are triggered by
46 appending additional v letters to the option (that is, -vv and
47 -vvv).
48
49 -e VIEWER, --viewer=VIEWER
50 Use trace viewer VIEWER to view the trace buffers. VIEWER is the
51 absolute path to the viewer command to use, and it can contain
52 command arguments as well. The trace directory paths are passed to
53 the VIEWER command as its last arguments.
54
55 Without this option, lttng crash uses babeltrace2(1) if it’s
56 available. Otherwise, it tries to use babeltrace(1).
57
58 Program information
59 -h, --help
60 Show help.
61
62 -V, --version
63 Show version.
64
66 0
67 Success
68
69 1
70 Error
71
72 3
73 Fatal error
74
76 If you encounter any issue or usability problem, please report it on
77 the LTTng bug tracker <https://bugs.lttng.org/projects/lttng-tools>.
78
80 • LTTng project website <https://lttng.org>
81
82 • LTTng documentation <https://lttng.org/docs>
83
84 • Git repositories <http://git.lttng.org>
85
86 • GitHub organization <http://github.com/lttng>
87
88 • Continuous integration <http://ci.lttng.org/>
89
90 • Mailing list <http://lists.lttng.org> for support and development:
91 lttng-dev@lists.lttng.org
92
93 • IRC channel <irc://irc.oftc.net/lttng>: #lttng on irc.oftc.net
94
96 This program is part of the LTTng-tools project.
97
98 LTTng-tools is distributed under the GNU General Public License version
99 2 <http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html>. See the
100 LICENSE <https://github.com/lttng/lttng-tools/blob/master/LICENSE> file
101 for details.
102
104 Special thanks to Michel Dagenais and the DORSAL laboratory
105 <http://www.dorsal.polymtl.ca/> at École Polytechnique de Montréal for
106 the LTTng journey.
107
108 Also thanks to the Ericsson teams working on tracing which helped us
109 greatly with detailed bug reports and unusual test cases.
110
112 lttng(1), lttng-sessiond(8), lttng-relayd(8), lttng-ust(3),
113 babeltrace2(1)
114
115
116
117LTTng 2.12.4 2 April 2020 LTTNG-CRASH(1)