table of contents
- bookworm 252.22-1~deb12u1
- bookworm-backports 254.5-1~bpo12+3
- testing 255.4-1
- unstable 255.4-1+b1
COREDUMPCTL(1) | coredumpctl | COREDUMPCTL(1) |
NAME¶
coredumpctl - Retrieve and process saved core dumps and metadata
SYNOPSIS¶
coredumpctl [OPTIONS...] {COMMAND} [PID|COMM|EXE|MATCH...]
DESCRIPTION¶
coredumpctl is a tool that can be used to retrieve and process core dumps and metadata which were saved by systemd-coredump(8).
COMMANDS¶
The following commands are understood:
list
The output is designed to be human readable and contains a table with the following columns:
TIME
PID
UID, GID
SIGNAL
COREFILE
EXE
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-coredump(8). 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.
info
dump
debug
OPTIONS¶
The following options are understood:
-h, --help
--version
--no-pager
--no-legend
--json=MODE
-1
-n INT
-S, --since
-U, --until
-r, --reverse
-F FIELD, --field=FIELD
-o FILE, --output=FILE
--debugger=DEBUGGER
-A ARGS, --debugger-arguments=ARGS
--file=GLOB
-D DIR, --directory=DIR
-q, --quiet
--all
MATCHING¶
A match can be:
PID
COMM
EXE
MATCH
EXIT STATUS¶
On success, 0 is returned; otherwise, a non-zero failure code is returned. Not finding any matching core dumps is treated as failure.
ENVIRONMENT¶
$SYSTEMD_DEBUGGER
EXAMPLES¶
Example 1. List all the core dumps of a program
$ coredumpctl list /lib64/firefox/firefox TIME PID UID GID SIG COREFILE EXE SIZE Tue ... 8018 1000 1000 SIGSEGV missing /lib64/firefox/firefox n/a Wed ... 251609 1000 1000 SIGTRAP missing /lib64/firefox/firefox n/a Fri ... 552351 1000 1000 SIGSEGV present /lib64/firefox/firefox 28.7M
The journal has three entries pertaining to /lib64/firefox/firefox, and only the last entry still has an available core file (in external storage on disk).
Note that coredumpctl needs access to the journal files to retrieve the relevant entries from the journal. Thus, an unprivileged user will normally only see information about crashing programs of this user.
Example 2. Invoke gdb on the last core dump
$ coredumpctl debug
Example 3. Use gdb to display full register info from the last core dump
$ coredumpctl debug --debugger-arguments="-batch -ex 'info all-registers'"
Example 4. Show information about a core dump matched by PID
$ coredumpctl info 6654
PID: 6654 (bash)
UID: 1000 (user)
GID: 1000 (user)
Signal: 11 (SEGV)
Timestamp: Mon 2021-01-01 00:00:01 CET (20s ago)
Command Line: bash -c $'kill -SEGV $$'
Executable: /usr/bin/bash
Control Group: /user.slice/user-1000.slice/...
Unit: user@1000.service
User Unit: vte-spawn-....scope
Slice: user-1000.slice
Owner UID: 1000 (user)
Boot ID: ...
Machine ID: ...
Hostname: ...
Storage: /var/lib/systemd/coredump/core.bash.1000.....zst (present)
Disk Size: 51.7K
Message: Process 130414 (bash) of user 1000 dumped core.
Stack trace of thread 130414:
#0 0x00007f398142358b kill (libc.so.6 + 0x3d58b)
#1 0x0000558c2c7fda09 kill_builtin (bash + 0xb1a09)
#2 0x0000558c2c79dc59 execute_builtin.lto_priv.0 (bash + 0x51c59)
#3 0x0000558c2c79709c execute_simple_command (bash + 0x4b09c)
#4 0x0000558c2c798408 execute_command_internal (bash + 0x4c408)
#5 0x0000558c2c7f6bdc parse_and_execute (bash + 0xaabdc)
#6 0x0000558c2c85415c run_one_command.isra.0 (bash + 0x10815c)
#7 0x0000558c2c77d040 main (bash + 0x31040)
#8 0x00007f398140db75 __libc_start_main (libc.so.6 + 0x27b75)
#9 0x0000558c2c77dd1e _start (bash + 0x31d1e)
Example 5. Extract the last core dump of /usr/bin/bar to a file named bar.coredump
$ coredumpctl -o bar.coredump dump /usr/bin/bar
SEE ALSO¶
systemd-coredump(8), coredump.conf(5), systemd-journald.service(8), gdb(1)
systemd 251 |