core-dumps

# List recent crashes
coredumpctl list
 
# Show details of the latest crash
coredumpctl info
 
# Load latest crash in GDB
coredumpctl gdb
 
# Load specific PID crash
coredumpctl gdb 12345
 
# Export core file
coredumpctl dump -o myapp.core PID

# macOS uses /cores by default (must be root-writable)
ulimit -c unlimited
 
# Check
ls /cores/
 
# launchd-launched services: set in plist
# <key>HardResourceLimits</key>
# <dict><key>Core</key><integer>9223372036854775807</integer></dict>

# Load binary and core
gdb ./prog core.12345
 
# If the binary was stripped, provide the unstripped copy
gdb ./prog-with-symbols core.12345
 
# Essential first commands
(gdb) bt                    # call stack
(gdb) bt full               # stack + locals
(gdb) info registers        # CPU state at crash
(gdb) frame 2               # jump to interesting frame
(gdb) info locals           # local variables in frame
(gdb) print ptr             # inspect a pointer
 
# All threads (multi-threaded crash)
(gdb) thread apply all bt full

lldb ./prog -c core.12345
 
# Or
lldb
(lldb) target create ./prog --core core.12345
 
# Commands
(lldb) bt
(lldb) thread backtrace all
(lldb) frame select 2
(lldb) frame variable

# Install client (Debian/Ubuntu)
sudo apt install debuginfod
 
# Enable (add to ~/.bashrc or /etc/environment)
export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com https://debuginfod.elfutils.org"
 
# GDB auto-fetches symbols when DEBUGINFOD_URLS is set
gdb ./prog core
 
# Manually query
debuginfod-find debuginfo <build-id>
debuginfod-find source <build-id> /path/to/file.c

# Check if binary has a build ID
readelf -n ./prog | grep Build
 
# Find the correct debug package
# Debian: apt install prog-dbg or prog-dbgsym
# RPM: dnf install prog-debuginfo
 
# Point GDB to debug symbols directory
(gdb) set debug-file-directory /usr/lib/debug
 
# Or use eu-readelf to dump build ID, then find .debug file
eu-readelf -n ./prog
find /usr/lib/debug -name "*.debug" | xargs eu-readelf -n 2>/dev/null | grep <build-id>

# Build
gcc -g -O2 -o prog main.c
 
# Separate debug info
objcopy --only-keep-debug prog prog.debug
objcopy --strip-debug prog prog.stripped
 
# Add a debuglink so GDB finds the debug file automatically
objcopy --add-gnu-debuglink=prog.debug prog.stripped
 
# Deploy prog.stripped; keep prog.debug in a symbols store indexed by build-id

# Print backtrace non-interactively
gdb -batch -ex 'bt full' -ex 'thread apply all bt full' ./prog core 2>&1 | tee crash.txt
 
# Print registers
gdb -batch -ex 'info registers' ./prog core
 
# Check signal that caused crash
gdb -batch -ex 'info signal' ./prog core