dotnet-debugging

Diagnoses crashes, hangs, high CPU, memory leaks and deadlocks from Windows, Linux, macOS dotnet dumps and live processes.

46|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill dotnet-debugging-sunyonghuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-debugging
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/.github/skills/dotnet-debugging
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill dotnet-debugging-sunyonghuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork from broken .NET, native, and mixed-mode applications by turning crash dumps, hangs, high CPU, and memory pressure into evidence-based root cause analysis.

Core Features & Use Cases

  • Crash dump analysis for Windows, Linux, and macOS using WinDbg MCP, dotnet-dump, LLDB with SOS, and createdump.
  • Hang, deadlock, and thread starvation triage with stack inspection, lock analysis, and wait-chain diagnosis.
  • High CPU and memory leak investigations that identify hot threads, heap growth, GC pressure, and retained objects.
  • Production and container diagnostics with dotnet-monitor, Docker, Kubernetes, symbol setup, and structured reporting.
  • Use case: investigate a customer report that an app froze after deployment, collect the right dump, inspect the critical threads, and produce a prioritized remediation plan.

Quick Start

Use the dotnet-debugging skill to analyze the attached dump or live process and return the most likely root cause with the key evidence that supports it.

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 from a dump file?

To diagnose a hang and deadlock, you inspect thread stacks and wait chains to identify blocked resources. This skill triages thread starvation and lock analysis using LLDB with SOS or WinDbg to pinpoint the exact blocking root cause.

Can I use dotnet-monitor for production container triage?

Yes, you can use dotnet-monitor for production container triage in Docker and Kubernetes. This skill covers collecting dumps from live processes and applying scenario-specific command packs for structured evidence-based reporting.

What is the best way to find high CPU and memory leaks in a .NET process?

The best way to find high CPU and memory leaks is by identifying hot threads and inspecting heap growth or retained objects. This skill analyzes GC pressure and memory allocation patterns to isolate the exact leaking components.

Does .NET crash analysis work across both Windows and Linux?

.NET crash analysis works across Windows, Linux, and macOS using platform-specific tools like WinDbg, dotnet-dump, and createdump. This skill configures symbols and inspects dumps to deliver consistent root cause analysis regardless of the operating system.

Why do I need to configure symbols for dotnet-dump debugging?

You need to configure symbols for dotnet-dump debugging to resolve function names and line numbers in call stacks. Without proper symbol setup, thread and heap inspection cannot translate memory addresses into actionable evidence for crash or hang diagnosis.