coredump

Analyze Linux core dumps in gdb to identify crash root causes via backtraces and frames.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Core Dump Analysis helps engineers quickly diagnose crashes by examining core dumps and performing post-mortem debugging to identify root causes.

Core Features & Use Cases

  • Enable core dumps for target applications using system settings.
  • Generate and load core files into gdb to obtain backtraces, inspect locals, and examine registers.
  • Reproduce issues offline and perform step-by-step analysis to guide fixes.

Quick Start

Run your application to trigger a crash and then load the generated core file in gdb to perform a post-mortem analysis.

Frequently Asked Questions about coredump

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

FAQPage Schema
How do I analyze a core dump to find the root cause of a crash?

To analyze a core dump, load the generated core file into gdb to perform a post-mortem analysis. You can obtain backtraces, inspect local variables, and examine registers to identify the root cause of the Linux application crash.

How do I enable core dumps for a Linux application?

You can enable core dumps for target Linux applications by adjusting system settings. Once enabled, running your application to trigger a crash will generate a core file suitable for offline analysis.

Can I reproduce and debug an early startup crash offline?

Yes, you can reproduce issues offline by loading the saved core file into gdb. This allows step-by-step analysis of early startup crashes and fatal signals without needing the live environment.

What is the best way to inspect local variables and frames after a fatal signal?

The best way to inspect local variables and frames after a fatal signal is to perform post-mortem debugging with gdb. Loading the core dump allows you to execute backtraces and analyze individual frames to guide fixes.