dump-collect
FeaturedConfigure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb/windbg/dotnet-dump analyze, profiling or tracing, or for .NET Framework processes.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- dotnet
- Repository
- dotnet/skills
- Created
- 9 months ago
- Last Updated
- today
- Language
- C#
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content โ not just same category
dotnet-trace-collect
Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).
debug-dumps
Analyze and debug Windows crash dumps (.dmp) and app crashes for Agentmaster (the C++/WinRT WindowsTerminal fork) WITHOUT cdb/WinDbg โ using the in-repo DIA-SDK + DbgHelp tools. Covers the whole loop: find the crash (WER Application Error event id 1000 + the full dump in %LOCALAPPDATA%\CrashDumps), read the exception record + faulting registers (dumpexc), decode what it means (0xC0000005 access violation, 0xC0000409 __fastfail incl. the CFG subcode 0xA freed-vtable, 0xC000027B stowed fail-fast, the 0xDDDDDDDD "dead-land" freed-memory register signature, non-canonical -1 faultData), walk the faulting-thread stack (dumpwalk2 ordered StackWalkEx; dumpourscan full-stack scan for OUR frames with a module histogram; dumpstack/hangwalk fallbacks), and symbolize OUR frames against the matching build's PDBs to pin the exact source line + root cause. Encodes the hard-won patterns: matching the PDB to the CRASHED binary by build time, "zero of our frames == a deferred/async XAML fail-fast off our call stack (uncatchable
crash-analysis
Analyzing core dumps, stack traces, and unhandled exceptions