dump-collect

Configure and collect crash dumps for .NET applications across platforms and containers.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/kierunb/ReliableAppDemo --skill dump-collect-kierunb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dump-collect
Source: https://github.com/kierunb/ReliableAppDemo/tree/main/.github/skills/dotnet-diag/skills/dump-collect
Command: npx skills add https://github.com/kierunb/ReliableAppDemo --skill dump-collect-kierunb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configure and collect crash dumps for modern .NET applications (CoreCLR and NativeAOT) across Linux, macOS, Windows, and container runtimes, enabling reliable diagnostic collection without requiring in-app changes.

Core Features & Use Cases

  • Automatic crash dumps for CoreCLR using DOTNET_DbgEnableMiniDump and related env vars
  • OS-level core dumps and createdump workflows for NativeAOT, including containerized deployments
  • On-demand dump collection from running processes using dotnet-dump collect (CoreCLR) or gcore (NativeAOT), with Docker/Kubernetes support
  • Verification guidance and dump-path reporting to ensure dumps are written and accessible

Quick Start

Enable automatic crash dumps by setting DOTNET_DbgEnableMiniDump and related env vars, ensure a dumps directory exists, then use dotnet-dump collect or gcore to capture dumps when needed.

Frequently Asked Questions about dump-collect

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

FAQPage Schema
How do I configure automatic crash dumps for .NET CoreCLR applications?

Enable automatic crash dumps for .NET CoreCLR by setting the DOTNET_DbgEnableMiniDump environment variable, along with DOTNET_DbgMiniDumpType and DOTNET_DbgMiniDumpName, to capture dumps without in-app changes.

What's the best way to collect crash dumps from a .NET app running in Docker or Kubernetes?

Collect crash dumps from containerized .NET apps by using dotnet-dump collect for CoreCLR or gcore for NativeAOT, ensuring a writable dumps directory exists and verifying dump accessibility after collection.

Does NativeAOT support automatic crash dump generation like CoreCLR?

NativeAOT relies on OS-level core dumps and the createdump utility rather than the DOTNET_DbgEnableMiniDump environment variables used by CoreCLR, requiring different configuration steps for automatic crash dump generation.

How do I capture an on-demand dump from a running .NET process?

Capture on-demand dumps from running .NET processes by invoking dotnet-dump collect for CoreCLR applications or gcore for NativeAOT, then verify the dump file path to ensure diagnostic data is accessible.

What environment variables are required to enable .NET crash dumps in Linux containers?

Configure .NET crash dumps in Linux containers by setting DOTNET_DbgEnableMiniDump, DOTNET_DbgMiniDumpType, and DOTNET_DbgMiniDumpName, ensuring the target dumps directory is writable within the container runtime.

Can I collect crash dumps for modern .NET apps across different operating systems?

Crash dumps for modern .NET applications can be configured and collected across Linux, macOS, and Windows using dotnet-dump collect, createdump, and gcore, with environment variables and verification steps tailored per platform.