The DAC enum memory region needs to be more bullet proof

[mikem8361]

If the target runtime process is in early runtime initialization (like on pause on startup), the DAC enum memory API will cause the calling program (like createdump) to segfault and not fail gracefully.

For the specific case this issue was found, the GC wasn't initialized yet so g_gcDacGlobals.GetAddr() is null in EnumMemCLRStatic so enumerating the GC's global DAC table segfaults.

Tagging subscribers to this area: @tommcdon
Notify danmosemsft if you want to be subscribed.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.