SOS does not know about the pinned object heap

[davmason]

Looking through the code, I can see that DacpGcHeapDetails and GCHeapSnapShot have hardcoded generation limits. Now that the runtime has another heap these APIs will be incomplete.

The following SOS commands use DacpGcHeapDetails:

• !EEHeap
• !ListNearObj
• !GCWhere
• !GCHeapStat
• !FinalizeQueue

And these APIs use GCHeapSnapShot:

• !GCRoot
• !DumpStackObjects
• !DumpIL
• !TraverseHeap
• !DumpAsync
• !DumpHeap
• !VerifyHeap
• !VerifyObj
• !FindRoots

I haven't done any testing, but based on my reading of the code none of them should be broken, but they will not report objects out of the pinned object heap.

[leculver]

@tommcdon This should be a ship-blocking issue for .Net Core 5. We really shouldn't ship the runtime if SOS functionality is broken, If you guys are planning to fix it within the next month (or so) I won't bother filing a blocking issue over there.