-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fix enum memory code paths #57981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix enum memory code paths #57981
Conversation
|
Tagging subscribers to this area: @tommcdon, @krwq |
mikem8361
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I built/ran your changes under the SOS tests on Windows and Linux and everything passes.
We will need to backport to rc2 (release/6.0).
|
@cshung is there anything else needed before merging this PR? |
|
I am working on testing it under |
mikem8361
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Ran the SOS tests again on Windows and Linux.
|
/backport release/6.0 |
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1164449928 |
Fix #57960
This fixes a few things:
dac_gc_heapare no longer guaranteed to be matching the target, in fact, the fields are no longer contiguous, therefore we need to callDacEnumMemoryRegionon individual fields separately.dac_generation.The arguments passed into
DacEnumMemoryRegionshould correspond to the right target addresses.Beyond manual inspection, is there something we can run to make sure this is correct?