Feature request: Generate crash report

[Youssef1313]

Today we have CrashDump extension for MTP which generates a dump on crash. In .NET 6.0+, there is also DOTNET_EnableCrashReport which generates a json crash report.

There is also DOTNET_EnableCrashReportOnly in .NET 7.0+, which generates only the report without the dump.

See https://github.com/dotnet/runtime/blob/313982dff3457c8291e8b88cd99785f6920319f0/docs/design/coreclr/botr/xplat-minidump-generation.md#configurationpolicy for docs about these env variables.

Reasons to generate report:

1. Getting information from CI crashes on macOS when the dev doesn't have access to a macOS. Json is json and will provide info/hints on what's wrong, even if less powerful than a dump, better than nothing.
2. Avoid paying the cost of uploading large dump files in CI for simple applications where the json will simply provide sufficient information, or maybe in some CI environments where disk space might not even be sufficient to store the dump file, or low-cost setups which won't allow uploading big artifacts.

[bart-vmware]

What tools exist to analyze such dump files?

[Youssef1313]

@bart-vmware The crash report you mean? It's just a JSON file. I have never tried it before though, and it seems to be relevant for crashes, not for hangs.

[bart-vmware]

I just have no idea what information is in such a file, and how difficult it would be to extract useful information from it.

[Youssef1313]

From the documentation above:

generates a json formatted crash report which includes information about the threads and stack frames of the crashing application. The crash report name is the dump path/name with .crashreport.json appended.

So looks like it's mostly plain text of the call stacks of different threads in the crashing app.