coredump

Analyze core dumps with gdb to diagnose early startup crashes and segfaults.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill coredump-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coredump
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/coredump
Command: npx skills add https://github.com/multicam/ikigai-rev --skill coredump-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem debugging using core dumps to diagnose crashes that occur before gdbserver can attach.

Core Features & Use Cases

  • Post-mortem crash analysis using core dumps with gdb
  • Enable, locate, and analyze core files; inspect stack traces and variables
  • Use case: diagnose early startup crashes, segfaults, or fatal signals offline

Quick Start

Enable core dumps, reproduce the crash, then analyze the core with gdb.

Frequently Asked Questions about coredump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a segfault that crashes before gdbserver can attach?

Post-mortem debugging with core dumps captures the crash state offline, allowing gdb to inspect the stack trace and variables without needing gdbserver initialized during early startup.

How do I enable and locate core dumps for crash analysis?

Enable core dumps in your system settings, reproduce the crash to generate the core artifact, then locate the core file to begin offline analysis of fatal signals with gdb.

What is post-mortem core-dump debugging and when do I need it?

Post-mortem core-dump debugging analyzes crash failures offline using generated core artifacts and gdb. It is needed for diagnosing segfaults, fatal signals, and crashes during very early startup.

Can I use gdb to inspect variables in a core dump from an early startup crash?

Yes, gdb can inspect stack traces and variables in a core dump. This allows offline analysis of early startup crashes and fatal signals that occur before gdbserver initializes.

What's the best way to analyze fatal signals offline without reproducing them live?

Post-mortem debugging with core dumps is the best way to analyze fatal signals offline. Enable core dumps, reproduce the crash once to generate the artifact, then inspect it with gdb.

Does post-mortem core-dump debugging work for crashes during very early startup?

Yes, core-dump debugging specifically applies to crashes during very early startup before gdbserver initializes. It captures the crash state for offline gdb stack trace and variable inspection.