cdb-debugging

Automate cdb.exe execution to diagnose Windows application crashes and hangs.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/missdeer/skills --skill cdb-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdb-debugging
Source: https://github.com/missdeer/skills/tree/main/cdb-debugging
Command: npx skills add https://github.com/missdeer/skills --skill cdb-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the collection of diagnostic evidence from Windows applications, eliminating the need for manual, repetitive interaction with the WinDbg command-line interface during crash or hang analysis.

Core Features & Use Cases

  • Automated Crash Analysis: Automatically captures stack traces, exception records, and register states when an application crashes on startup or during execution.
  • Hang Diagnosis: Collects thread stacks and lock information for unresponsive processes to identify deadlocks or infinite loops.
  • Use Case: When a development build crashes on launch, use this skill to automatically run the executable under cdb, generate a full stack trace, and save the output to a log file for immediate review.

Quick Start

Use the cdb-debugging skill to analyze the crash of the application located in the build directory and save the diagnostic log to the tmp folder.

Frequently Asked Questions about cdb-debugging

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

FAQPage Schema
How do I automate Windows crash analysis to get a stack trace from cdb?

You can automate Windows crash analysis by running cdb.exe non-interactively to capture stack traces, exception records, and register states. This skill executes the debugging process automatically and saves the diagnostic output to a log file for immediate review.

What is the best way to diagnose an application hang or deadlock on Windows?

To diagnose a Windows application hang, this skill automates cdb to collect thread stacks and lock information from unresponsive processes. It identifies deadlocks or infinite loops by gathering diagnostic evidence without manual WinDbg interaction.

Do I need PDB files and Windows SDK Debugging Tools to run cdb for crash diagnostics?

Yes, you need a local installation of the Windows SDK Debugging Tools and matching PDB files. These are required for accurate symbol resolution when cdb analyzes your application's stack traces and exception context.

Can I capture exception context and module analysis for a development build that crashes on launch?

Yes, you can capture exception context and module analysis for a crashing development build. The skill runs the executable under cdb, automatically extracts the full stack trace, and saves the diagnostic logging output.

Why use automated cdb execution instead of manual WinDbg command-line interaction?

Automated cdb execution eliminates repetitive manual interaction with the WinDbg command-line interface. It automatically collects diagnostic evidence from Windows applications during crash or hang analysis, saving time and ensuring consistent evidence gathering.