coredumpctlsystemdcoredumpctl1coredumpctlRetrieve and process saved core dumps and metadatacoredumpctlOPTIONSCOMMANDPID|COMM|EXE|MATCHDescriptioncoredumpctl is a tool that can be used to retrieve and process core
dumps and metadata which were saved by
systemd-coredump8.
CommandsThe following commands are understood:listList core dumps captured in the journal
matching specified characteristics. If no command is
specified, this is the implied default.The output is designed to be human readable and contains a table with the following
columns:TIMEThe timestamp of the crash, as reported by the kernel.PIDThe identifier of the process that crashed.UIDGIDThe user and group identifiers of the process that crashed.SIGNALThe signal that caused the process to crash, when applicable.
COREFILEInformation whether the coredump was stored, and whether
it is still accessible: none means the core was
not stored, - means that it was not available (for
example because the process was not terminated by a signal),
present means that the core file is accessible by the
current user, journal means that the core was stored
in the journal, truncated is the
same as one of the previous two, but the core was too large and was not
stored in its entirety, error means that the core file
cannot be accessed, most likely because of insufficient permissions, and
missing means that the core was stored in a file, but
this file has since been removed.EXEThe full path to the executable. For backtraces of scripts
this is the name of the interpreter.It's worth noting that different restrictions apply to
data saved in the journal and core dump files saved in
/var/lib/systemd/coredump, see overview in
systemd-coredump8.
Thus it may very well happen that a particular core dump is still listed
in the journal while its corresponding core dump file has already been
removed.infoShow detailed information about the last core dump
or core dumps matching specified characteristics
captured in the journal.dumpExtract the last core dump matching specified
characteristics. The core dump will be written on standard
output, unless an output file is specified with
. debugInvoke a debugger on the last core dump
matching specified characteristics. By default,
gdb1
will be used. This may be changed using the
option or the $SYSTEMD_DEBUGGER environment
variable.OptionsThe following options are understood:Do not print column headers.Show information of a single core dump only, instead of listing
all known core dumps.Only print entries which are since the specified date.Only print entries which are until the specified date.Reverse output so that the newest entries are displayed first.
FIELDFIELDPrint all possible data values the specified
field takes in matching core dump entries of the
journal.FILEFILEWrite the core to .
DEBUGGERUse the given debugger for the debug
command. If not given and $SYSTEMD_DEBUGGER is unset, then
gdb1
will be used. Takes a file glob as an argument. If
specified, coredumpctl will operate on the specified journal
files matching GLOB instead of the
default runtime and system journal paths. May be specified
multiple times, in which case files will be suitably
interleaved.DIRDIRUse the journal files in the specified .
Suppresses informational messages about lack
of access to journal files and possible in-flight coredumps.
MatchingA match can be:PIDProcess ID of the
process that dumped
core. An integer.COMMName of the executable (matches
). Must not contain slashes.
EXEPath to the executable (matches
). Must contain at least one
slash. MATCHGeneral journalctl match filter, must contain an equals
sign (=). See
journalctl1.
Exit statusOn success, 0 is returned; otherwise, a non-zero failure
code is returned. Not finding any matching core dumps is treated as
failure.
Environment$SYSTEMD_DEBUGGERUse the given debugger for the debug
command. See the option.ExamplesList all the core dumps of a program named foo# coredumpctl list fooInvoke gdb on the last core dump# coredumpctl debugShow information about a process that dumped core,
matching by its PID 6654# coredumpctl info 6654Extract the last core dump of /usr/bin/bar to a file named
bar.coredump# coredumpctl -o bar.coredump dump /usr/bin/barSee Alsosystemd-coredump8,
coredump.conf5,
systemd-journald.service8,
gdb1