Core Dumps

mohitmishra786/low-level-dev-skills/skills/debuggers/core-dumps

作者 mohitmishra786bdc58472fa9f无许可证253 个星标收录于 2026年10月9日更新于 2026年10月9日仓库3个月前更新

Core dump analysis skill for production crash triage. Use when loading core files in GDB or LLDB, enabling core dump generation on Linux/macOS, mapping symbols with debuginfo or debuginfod, or extracting backtraces from crashes without re-running the program. Activates on queries about core files, ulimit, coredumpctl, debuginfod, crash triage, or analyzing segfaults from production binaries.

仅含说明Software DevelopmentDevOps & Cloud
AI 生成的概览

指导代理启用、收集并分析核心转储，以便用 GDB、LLDB 和 debuginfod 进行事后崩溃排查。

功能
该技能提供在 Linux 和 macOS 上启用核心转储生成的分步说明，包括 ulimit 设置、内核 core pattern 以及 systemd coredumpctl。它涵盖在 GDB 和 LLDB 中加载核心文件、提取调用栈、寄存器和局部变量，并通过 debuginfod 或手动调试包解析缺失的符号。它还介绍用 objcopy 分离调试信息以及以非交互批处理方式做快速排查。工作流附带一份参考速查表。
适用场景
当程序在生产环境崩溃、需要在不重新运行程序的情况下分析核心文件时使用。适用于有关核心文件、ulimit、coredumpctl、debuginfod、崩溃排查或生产二进制段错误分析的问题。
运行要求
需要 GDB 或 LLDB 等调试器，在 Linux 上可选 systemd coredumpctl、debuginfod 客户端工具、binutils（objcopy、readelf）和 elfutils。从 debuginfod 服务器获取符号可能需要网络访问。该技能不附带脚本，只有说明和一份参考速查表。

Core Dumps

Purpose

Guide agents through enabling, collecting, and analysing core dumps for post-mortem crash investigation without rerunning the buggy program.

Triggers

  • "My program crashed in production — how do I analyse the core?"
  • "How do I enable core dumps on Linux?"
  • "I have a core file but no symbols / source"
  • "How do I use debuginfod to get symbols for a core?"
  • "coredumpctl show me the crash"

Workflow

1. Enable core dumps (Linux)

bash
# Per-session (lost on logout)ulimit -c unlimited
# Persistent (add to /etc/security/limits.conf)*   soft   core   unlimited*   hard   core   unlimited
# Check current limitulimit -c
# Set core pattern (where and how cores are named)# Default: 'core' in CWD — often not usefulsudo sysctl -w kernel.core_pattern=/tmp/core-%e-%p-%t# %e = executable, %p = PID, %t = timestamp
# Persistent (add to /etc/sysctl.d/99-core.conf)kernel.core_pattern=/tmp/core-%e-%p-%tkernel.core_uses_pid=1

2. systemd/coredumpctl (modern Linux)

If systemd manages core dumps (common on Ubuntu 20+, Fedora, Arch):

bash
# List recent crashescoredumpctl list
# Show details of the latest crashcoredumpctl info
# Load latest crash in GDBcoredumpctl gdb
# Load specific PID crashcoredumpctl gdb 12345
# Export core filecoredumpctl dump -o myapp.core PID

Core storage location: /var/lib/systemd/coredump/.

3. Enable core dumps (macOS)

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

4. Analyse a core with GDB

bash
# Load binary and coregdb ./prog core.12345
# If the binary was stripped, provide the unstripped copygdb ./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

5. Analyse a core with LLDB

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

6. Missing symbols: debuginfod

debuginfod serves debug symbols from a central server, mapping build IDs to DWARF data.

bash
# 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 setgdb ./prog core
# Manually querydebuginfod-find debuginfo <build-id>debuginfod-find source <build-id> /path/to/file.c

7. Missing symbols: manual approach

bash
# Check if binary has a build IDreadelf -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 fileeu-readelf -n ./progfind /usr/lib/debug -name "*.debug" | xargs eu-readelf -n 2>/dev/null | grep <build-id>

8. Strip binaries and keep symbols

Best practice: build with symbols, strip for distribution, keep an unstripped copy.

bash
# Buildgcc -g -O2 -o prog main.c
# Separate debug infoobjcopy --only-keep-debug prog prog.debugobjcopy --strip-debug prog prog.stripped
# Add a debuglink so GDB finds the debug file automaticallyobjcopy --add-gnu-debuglink=prog.debug prog.stripped
# Deploy prog.stripped; keep prog.debug in a symbols store indexed by build-id

9. Quick triage from core without full debug session

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

For a full cheatsheet covering core pattern tokens, coredumpctl, GDB/LLDB commands, debuginfod servers, and strip/symbol workflows, see references/cheatsheet.md [blocked].

Related skills

  • Use skills/debuggers/gdb for full GDB session details
  • Use skills/debuggers/lldb for LLDB-based analysis
  • Use skills/runtimes/sanitizers to catch the bug before it reaches production
  • Use skills/binaries/elf-inspection for readelf, build IDs, and binary inspection

来源与署名

来源：mohitmishra786/low-level-dev-skills位于skills/debuggers/core-dumps提交bdc5847

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 mohitmishra786/low-level-dev-skills 的技能

Zig Debugging

mohitmishra786

指导使用 GDB、LLDB 调试 Zig 程序，解读 panic、错误返回追踪、日志记录及 IDE 配置。

Software Development2533个月前更新

Simd Intrinsics

mohitmishra786

指导使用 x86 SSE/AVX 与 ARM NEON 内建函数编写和诊断 SIMD 向量化。

Software Development2533个月前更新

Zig Cross

mohitmishra786

指导 Zig 交叉编译：目标三元组、CPU 特性、用 zig cc 编译 C、嵌入式与 WASM 目标。

Software Development2533个月前更新

Rustc Basics

mohitmishra786

指导 Rust 编译器配置：RUSTFLAGS、Cargo 配置文件、构建调优，以及查看 MIR 或汇编输出。

Software Development2533个月前更新

Zig Cinterop

mohitmishra786

指导 Zig 与 C 互操作：@cImport、translate-c、extern 与 packed 结构体，以及 C/Zig 混合构建。

Software Development2533个月前更新

Zig Build System

mohitmishra786

指导编写和调试 Zig 的 build.zig 文件，涵盖目标、C 源码、选项、测试与包清单。

Software Development2533个月前更新

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新