core-dumps

Core dump analysis for production triage uses GDB or LLDB to inspect crashed program state, revealing call stacks, registers, and local variables. This post-mortem debugging approach diagnoses segfaults and runtime errors without needing to reproduce the bug locally.

Load debug symbols for stripped binaries during core dump analysis by using `debuginfod` or manual methods to resolve build IDs. This symbol resolution maps memory addresses to source code lines, enabling effective debugging of production crashes.

Configure `ulimit` and `sysctl` to generate core dumps for production crash analysis on Linux and macOS. These settings ensure the operating system writes core files when applications segfault, providing the necessary state snapshots for post-mortem debugging.

When core dump analysis yields missing symbols or unresolved build IDs, use `debuginfod` to automatically fetch debug symbols for stripped binaries. This resolves mapping issues and restores source code visibility during GDB and LLDB post-mortem triage workflows.

GDB and LLDB both support core dump analysis, with GDB commonly used on Linux and LLDB on macOS. Both debuggers inspect crashed program state, call stacks, and registers, and can leverage `debuginfod` for resolving symbols in stripped production binaries.

Core dump analysis requires configuring `ulimit` and `sysctl` on Linux or macOS to generate core files upon application crashes. This environment setup ensures production services produce the necessary state snapshots for post-mortem debugging with GDB or LLDB.