Original issue below. Going to track the tasks:

• Log a breadcrumb with the crash reason ([merp] Create a signal ('source') breadcrumb for the crash dump process #19072 - master)
• Add a managed API to extract the crash reason from a directory containing breadcrumbs (not sure about this - @kdubau I think this bit belongs in some library outside the runtime (but kept in sync with the runtime)
• Log a breadcrumb with the stack hash once we know it ([merp] Add breadcrumb for StackHash #19240)
• Add a managed API to extract the stack hash from a directory containing breadcrumbs (same caveat)

Currently MERP logs the crash phase breadcrumb/files during MERP report generation. We use this to measure MERP success rate with VSM telemetry (as seen in https://work.azdo.io/1060810).

However, we do not know what type of report was being generated. It would be helpful if Mono could log the signal type (SigAbrt, SigSegv, SigTerm, SigManaged, etc.) so we can also send via telemetry the type of crash that was being worked on.

This should happen as early in the mono_summarize_phase timeline as possible.

This is https://work.azdo.io/1062126