dotnet-debugging

Diagnose .NET application crashes, hangs, and memory leaks across platforms.

1|1|Updated Mar 7, 2026

Search Tags:#debugging #memory leaks #.net #crash analysis #hangs #linux debugging #winDbg

Ready to run

npx skills add https://github.com/itsmichaelwest/agent-kit --skill dotnet-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-debugging
Source: https://github.com/itsmichaelwest/agent-kit/tree/main/skills/dotnet-debugging
Command: npx skills add https://github.com/itsmichaelwest/agent-kit --skill dotnet-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive solution for diagnosing and resolving issues in .NET applications across Windows, Linux, and macOS, including complex scenarios like crashes, hangs, and memory leaks.

Core Features & Use Cases

Cross-Platform Debugging: Supports WinDbg (Windows), dotnet-dump, and LLDB (Linux/macOS) for analyzing live processes and crash dumps.
Advanced Triage: Handles crash dumps, application hangs, high CPU usage, memory leaks, and kernel debugging.
Container Diagnostics: Includes patterns for debugging .NET applications within Docker and Kubernetes environments.
Use Case: Your .NET application is experiencing intermittent hangs on a Linux server. Use this Skill to collect a dump, analyze thread contention, and identify the root cause of the deadlock.

Quick Start

Use the dotnet-debugging skill to analyze a crash dump file located at '/tmp/myapp.dmp'.

Frequently Asked Questions about dotnet-debugging

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

FAQPage Schema

How do I debug a .NET application hang on Linux?▼

Debug a .NET application hang on Linux by collecting a process dump with dotnet-dump, then analyzing thread contention using LLDB with SOS to identify the deadlock root cause.

Can I analyze .NET memory leaks from crash dumps across different operating systems?▼

Yes, you can analyze .NET memory leaks from crash dumps across Windows, Linux, and macOS using WinDbg, dotnet-dump, and LLDB with SOS to inspect heap objects and diagnose high memory usage.

What is the best way to diagnose .NET applications in Docker and Kubernetes containers?▼

The best way to diagnose .NET applications in Docker and Kubernetes containers is to use container diagnostics patterns that support live process analysis and crash dump collection to resolve production issues.

Does dotnet-monitor work for production monitoring of .NET application crashes?▼

Yes, dotnet-monitor works for production monitoring of .NET application crashes, allowing you to collect dumps and trace live processes to triage high CPU usage, hangs, and memory leaks.

How do I analyze a crash dump file to find the root cause of a .NET application crash?▼

To analyze a crash dump file and find the root cause of a .NET application crash, load the dump file into WinDbg or LLDB with SOS to inspect thread states, call stacks, and memory objects.

When do I need WinDbg versus LLDB for .NET debugging?▼

You need WinDbg for .NET debugging on Windows, while LLDB with SOS is used for diagnosing crashes, hangs, and memory leaks on Linux and macOS environments.