[Feature Request] Linux crash dump generation: Support creating both Minidump and Full Dump on a single crash event
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
### Description
Currently on Linux, the .NET crash dump infrastructure allows configuring a single dump type for crash dump generation (e.g., Minidump, Heap Dump, or Full Dump) through `DOTNET_DbgMiniDumpType` / `createdump` settings. However, there is no built-in mechanism to generate both a `Mini` dump and a `Full` dump for the same crash event.
For production services, both dumps are valuable:
- Minidump
- Smaller size
- Faster to upload for analysis
- Easier to attach to incidents and automated diagnostics workflows
- Full Dump
- Preserves complete process memory
- Enables deep root-cause analysis when minidump data is insufficient
Today, we can choose only one of the dump types.
### Requested Enhancement
Provide a supported mechanism to generate both a `Mini` dump and a `Full` dump from the same crash event.
Contributor guide
Research direction
Start by reading the Linux crash-dump implementation around createdump and the DOTNET_DbgMiniDumpType configuration mentioned in the issue. Determine where a single dump type is selected and identify the existing tests or entry points covering crash-event dump generation; done means a supported way to produce both Mini and Full dumps from one crash event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100