Add loader heap enumeration api's (ICorDebugProcess11)

[hoyosjs]

It's easier to review by commit and ignore the second commit and whitespace

[ghost]

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

[jkotas]

Is it just to make the broken eeheap SOS command work, or do we have a real end-to-end diagnostic experience in mind for this?

FWIW, I do not think that the SOS command that enumerates the loader heaps is particularly useful. I have filled the issue because of somebody reported it via email.

[davmason]

This is a request from the VS team, they want to be able to know if a memory address is either on the GC heap (there's already an API for getting the GC heap segments) or on the runtime's loader heap (this API). They will use it to do some heuristics about what data target to read from in a managed TTT

[noahfalk]

LGTM : )

[ghost]

Hello @hoyosjs!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

1. DotNet Maestro - Int
2. DotNet Maestro
3. Dependabot

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this

From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at fabricbotservices@microsoft.com to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

[hoyosjs]

@Anipik do you know where these came from? These look like services/bot accounts. Do we have a check for them?