skills.rest
sayedihashimi
sayedihashimiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dotnet-debugging

Diagnose crashes, hangs, and memory issues in .NET apps with WinDbg, dotnet-dump, SOS, and LLDB.

2|Updated Mar 17, 2026
Search Tags:#memory#crash#windbg#hang#sos#dotnet-debugging#dumps
One-click install
npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-debugging-sayedihashimi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-debugging
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-artisan/skills/dotnet-debugging
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-debugging-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging Windows and Linux/macOS applications (native, managed, or mixed-mode) to diagnose crashes, hangs, high CPU, and memory issues using WinDbg MCP, dotnet-dump, SOS, and LLDB, with production diagnostics in containerized environments.

Core Features & Use Cases

  • Structured diagnostic workflows for crash, hang, high-CPU, and memory triage across Windows, Linux, and containers
  • Unified toolchain: WinDbg MCP for Windows, dotnet-dump/createdump for cross-platform, and LLDB SOS for native+managed analysis
  • Reference-driven guidance and scenario packs to reproduce and verify fixes

Quick Start

Attach the appropriate debugger (WinDbg MCP, dotnet-dump, or LLDB SOS) to a target process or dump and follow the guided command packs to diagnose crashes, hangs, or memory issues.

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 crash using WinDbg and SOS?▼

To debug a .NET application crash, attach WinDbg to the target process or crash dump and use SOS commands to inspect the managed heap and identify the failing thread. Following structured diagnostic workflows ensures repeatable, auditable crash analysis results.

Can I use dotnet-dump to collect and analyze memory dumps from Linux containers?▼

Yes, dotnet-dump and createdump support cross-platform production diagnostics, allowing you to collect and analyze memory and crash dumps from Linux and containerized .NET applications. You can then inspect these dumps using guided diagnostic command packs.

What is the best way to diagnose high CPU and hang issues in mixed-mode .NET apps?▼

Diagnosing high CPU and hang issues in mixed-mode .NET apps requires a unified toolchain like WinDbg MCP or LLDB with the SOS extension. These tools enable native and managed stack inspection to pinpoint blocking threads and resource contention.

Do I need to configure symbols before analyzing crash dumps with WinDbg?▼

Yes, proper symbol configuration is required before analyzing crash dumps with WinDbg to resolve function names and stack frames accurately. Without correct symbols, diagnostic command packs cannot produce meaningful or auditable results.

How does LLDB with SOS compare to WinDbg for cross-platform .NET debugging?▼

WinDbg MCP is tailored for Windows environments, whereas LLDB with SOS provides native and managed debugging capabilities across Linux and macOS. Both apply structured diagnostic workflows to analyze crashes, hangs, and memory issues.

Why is my dotnet-dump analysis not resolving managed memory issues correctly?▼

Managed memory analysis failures using dotnet-dump typically stem from missing symbols or using an incompatible SOS version for the target .NET runtime. Ensuring proper tool installation and symbol paths is necessary for accurate heap inspection.

Related Skills

Explore More Software Engineering Skills→
itsmichaelwestitsmichaelwest
1

dotnet-debugging

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

Community
Advanced
sunyonghuansunyonghuan
46

dotnet-debugging

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

Community
Advanced
ojrojasojrojas

dotnet-trace-collect

Guide diagnostic artifact capture for .NET performance analysis.

Community
Advanced
rudironsonirudironsoni

dotnet-profiling

Diagnose .NET performance issues using dotnet-counters, dotnet-trace, and dotnet-dump.

Community
Advanced