dotnet-windbg-debugging

Analyze Windows crash dumps and live processes with WinDbg.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/rudironsoni/SharpClaw --skill dotnet-windbg-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-windbg-debugging
Source: https://github.com/rudironsoni/SharpClaw/tree/main/.github/skills/dotnet-windbg-debugging
Command: npx skills add https://github.com/rudironsoni/SharpClaw --skill dotnet-windbg-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables deep debugging of Windows applications, including .NET and native code, by leveraging the powerful WinDbg debugger for crash, hang, and performance issue analysis.

Core Features & Use Cases

  • Crash Dump Analysis: Investigate .dmp files for any Windows process.
  • Live Debugging: Attach to running processes via a debug server.
  • Hang and Performance Triage: Diagnose deadlocks, high CPU, and memory pressure.
  • Use Case: When a critical Windows service crashes intermittently, use this Skill to analyze the generated crash dump to pinpoint the root cause in the code.

Quick Start

Use the dotnet-windbg-debugging skill to analyze the crash dump file 'myapp.dmp'.

Frequently Asked Questions about dotnet-windbg-debugging

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

FAQPage Schema
How do I analyze a Windows crash dump file for a .NET application?

You can analyze a Windows crash dump file by loading the .dmp file into a WinDbg session. This Skill processes crash dumps for native, managed, or mixed-mode .NET applications to pinpoint root causes.

Can I attach WinDbg to a live running process to diagnose a hang?

Yes, you can attach WinDbg to a live process via a debug server. This allows you to perform hang and performance triage to diagnose deadlocks, high CPU, and memory pressure.

Does WinDbg debugging support mixed-mode applications with both native and .NET code?

Yes, WinDbg debugging supports mixed-mode applications. It analyzes crash dumps and live processes for native, managed (.NET/CLR), or mixed-mode Windows user-mode applications.

What is the best way to triage high CPU usage in a Windows service?

The best way to triage high CPU usage is to use WinDbg for performance triage. This Skill investigates running processes or crash dumps to diagnose high CPU, memory pressure, and deadlocks.

How does structured diagnostic reporting work for crash analysis?

Structured diagnostic reporting works by using structured command packs and report templates during crash analysis. This Skill leverages these to provide structured reports for Windows application triage.

What do I need to debug intermittent Windows service crashes?

To debug intermittent Windows service crashes, you need the generated crash dump file. Use this Skill to analyze the dump file and pinpoint the root cause within the code.