LTTNG-CRASH(1)

📦
version 2.15.1 · 9 versions
, in nixpkgs unstable, ubuntu stonking

💥 LTTNG-CRASH(1) 💥

okay so bestie, this page comes to you straight out of the LTTng Manual, section 1, and it is genuinely one of my faves because it's the tool that shows up when everything has already gone wrong. crisis management, but make it chic. 🫶

✨ NAME ✨

lttng-crash — recover and read LTTng trace buffers in the event of a crash 🔥

✨ SYNOPSIS ✨

lttng-crash [--extract=DIR | --viewer=READER] [-verbose]... SHMDIR

✨ DESCRIPTION ✨

The Linux Trace Toolkit: next generation (https://lttng.org/) is an open-source software package used for correlated tracing of the Linux kernel, user applications, and user libraries. obsessed with her actually.

So LTTng is made of two things: Linux kernel modules (that's your Linux kernel tracing 🌸) and dynamically loaded libraries (that's your user application and library tracing 🦋).

And the lttng-crash command-line tool? She recovers LTTng trace buffers in the event of a system crash. yes, in the event of a crash. your system fell over, and she's still cute, still working. 💅

Here's the vibe: lttng-crash reads the files inside the SHMDIR directory, and then does one of these two things:

  • Without the --extract option — she launches a trace reader (peep the --viewer option 👀) so you can look at the traces she recovered.
  • With the --extract=DIR option — she extracts the files as uncorrupted LTTng traces into the DIR directory. pristine. no corruption. we love a clean recovery. ✨

And SHMDIR? That's the directory you passed as the argument of the --shm-path option of the lttng-create(1) command you used to create the recording session you're now desperately trying to recover. iykyk.

✨ OPTIONS ✨

  • -x DIR, --extract=DIR — extract the recovered traces into the directory DIR, and do NOT execute any trace reader. no reader, just files. periodt.
  • -v, --verbose — increase verbosity 🗣️

Specify this option up to three times to get more levels of verbosity. stack 'em, bestie.

  • -e READER, --viewer=READER — use the trace reader READER to read the trace buffers.

READER is the absolute path to the reader command to use, and it can contain command arguments as well. lttng-crash passes the trace directory paths to the READER command as its last arguments.

Without this option, lttng-crash uses babeltrace2(1) if it's available. Otherwise, it tries to use babeltrace(1). she's got backups for her backups. 🌈

🌸 Program information 🌸

  • -h, --help — show help.

This option attempts to launch /usr/bin/man to view this manual page. Override the manual pager path with the LTTNG_MAN_BIN_PATH environment variable. if you've got opinions about pagers, that's your moment. 💜

  • --list-options — list the available command options and quit.
  • -V, --version — show version and quit.

✨ EXIT STATUS ✨

  • 0 — success 🎉
  • 1 — error 😭
  • 3 — fatal error 💀

✨ RESOURCES ✨

This program is part of the LTTng-tools project.

LTTng-tools is distributed under the GNU General Public License version 2 (http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html). See the LICENSE file (https://github.com/lttng/lttng-tools/blob/master/LICENSE) for details. 📜

✨ THANKS ✨

Special thanks to Michel Dagenais and the DORSAL laboratory (http://www.dorsal.polymtl.ca/) at École Polytechnique de Montréal for the LTTng journey. 🫶

Also thanks to the Ericsson teams working on tracing, which helped us greatly with detailed bug reports and unusual test cases. the unusual test cases are the real mvps fr fr. 😭

✨ SEE ALSO ✨

babeltrace2(1), lttng(1), lttng-create(1) 🦋

so yeah, that's the whole thing. this page is from LTTng 2.15.1, dated 14 June 2021, and it lives in section 1 of the manual. go forth and recover your traces, bestie, you've got this. 💅✨🎀

📦 where this page comes from