coredump_diagnose

Name: coredump_diagnose
Availability: InStock
Author: linfordwu

Diagnose Linux user-space core dumps via a gdb-driven analysis workflow.

1|1|Updated Apr 25, 2026

Search Tags:#diagnostics #linux #gdb #stack-trace #crash-analysis #coredump #memory-diagnosis

Ready to run

npx skills add https://github.com/linfordWu/owls --skill coredump-diagnose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coredump_diagnose
Source: https://github.com/linfordWu/owls/tree/main/skills/coredump_diagnose
Command: npx skills add https://github.com/linfordWu/owls --skill coredump-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gdb, readelf, file, timeout, awk, sed, grep, objdump, python3-dbg, and includes scripts (resource) components.

What problem does it solve?

Diagnoses Linux user-space core dumps by orchestrating a deterministic gdb-driven analysis workflow to determine crash causes and provide actionable insights.

Core Features & Use Cases

Structured workflow: from pre-check to deep-dive analysis across multiple crash scenarios.
Scenario-driven guidance: handles common crash classes (nullptr, stack overflow, memory corruption, abort, divzero, sigbus) with targeted scripts.
Operational outputs: logs written to /tmp/core_diag and reusable reports for archiving and debugging.
Use case: a developer uses a core from a failing Linux daemon and runs the skill to produce a root-cause hypothesis and recommended fixes.

Quick Start

Run the top-level skill to begin automatic diagnosis on a Linux core dump.

Frequently Asked Questions about coredump_diagnose

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

FAQPage Schema

How do I diagnose a Linux core dump to find the root cause of a crash?▼

To diagnose a Linux core dump, you can run a structured gdb-driven analysis workflow that identifies crash root causes like null pointers or memory corruption. This process generates actionable insights and saves structured reports to /tmp/core_diag.

Can I use gdb to analyze common crash signals like SIGSEGV and SIGABRT?▼

Yes, you can use gdb to analyze common crash signals like SIGSEGV and SIGABRT. The analysis workflow targets specific crash scenarios including stack overflows, memory corruption, and use-after-free, providing targeted diagnosis for each signal type.

What do I need to analyze a core dump on Linux?▼

To analyze a core dump on Linux, you need GNU gdb installed, access to the core file and the corresponding binary. The workflow relies on standard Linux utilities like readelf, file, and objdump to execute the deterministic analysis.

What is the best way to automate memory corruption diagnosis for Linux applications?▼

The best way to automate memory corruption diagnosis is using a deterministic gdb-driven workflow that outputs structured reports suitable for automation and archiving. It handles scenario-driven guidance for use-after-free and memory corruption crashes.

Does core dump analysis work with Python applications?▼

Yes, core dump analysis works with Python applications when the python3-dbg dependency is installed. The gdb-driven workflow can process the core dump to identify crash root causes and generate reusable reports for debugging.

What are the limitations of using gdb for crash analysis on Linux?▼

Limitations of using gdb for crash analysis include the requirement of having the exact binary and core file accessible. The scope is limited to user-space crashes involving common signals like SIGSEGV, SIGBUS, SIGABRT, and SIGFPE.