dotnet-debugging

Triage Windows crash dumps and live process issues with WinDbg.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill dotnet-debugging-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-debugging
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/dotnet-debugging
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill dotnet-debugging-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you rapidly identify the root cause of Windows application failures by guiding WinDbg-based debugging of crash dumps and live process issues for native, managed, and mixed-mode scenarios.

Core Features & Use Cases

  • Crash, hang, and high-CPU triage: Uses repeatable WinDbg workflows (including SOS) to extract exception context, thread state, and likely hotspots.
  • Memory leak and memory pressure investigation: Correlates managed heap evidence with native heap signals to assess leak versus transient pressure.
  • Production-ready reporting: Produces structured diagnostic summaries with evidence-oriented recommendations using the provided report templates.

For example, when a .NET service crashes intermittently in production, you can load the dump, analyze the exception and managed call stacks, inspect threads, and generate an evidence-backed report with next-step recommendations.

Quick Start

Ask the assistant to analyze a crash dump for high-confidence root cause by loading the dump, fixing symbols, running the crash/hang/high-CPU task workflow, and filling the diagnostic report template.

Frequently Asked Questions about dotnet-debugging

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

FAQPage Schema
How do I diagnose a .NET application crash dump using WinDbg?

To diagnose a .NET crash dump, load the dump in WinDbg, configure symbols, load SOS for CLR, and run the crash triage workflow to extract exception context and managed call stacks for an evidence-backed root cause.

What is the best way to investigate high-CPU runaway threads in a .NET hang diagnosis?

The best way to investigate high-CPU runaway threads during a .NET hang diagnosis is using WinDbg to inspect live process thread state and SOS to extract managed hotspot evidence, avoiding speculative conclusions.

Does WinDbg debugging work for mixed-mode native and .NET memory leak investigations?

Yes, WinDbg debugging works for mixed-mode memory leak investigation by correlating managed heap evidence from SOS with native heap signals to assess whether the issue is a leak or transient memory pressure.

Do I need to configure symbols before loading SOS for .NET crash triage?

Yes, you need proper symbol configuration in WinDbg before loading SOS for .NET crash triage, as symbols are required to resolve native and managed call stacks accurately during crash and hang diagnosis.

Can I use WinDbg to diagnose both live process hangs and kernel-dump crashes?

Yes, you can use WinDbg to diagnose both live process hangs and kernel-dump crashes, applying scenario-based command packs to triage user-mode issues and kernel-dump workflows with structured evidence reporting.