Skip to content
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

Move computation of DebuggerAssemblyControlFlags from DomainAssembly to Assembly #107809

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

elinor-fung
Copy link
Member

@elinor-fung elinor-fung commented Sep 13, 2024

This moves the initial computation into Assembly and removes the flags from DomainAssembly. Actual consumers were already getting the flags off of Assembly or Module

cc @jkotas @AaronRobinsonMSFT

Copy link
Contributor

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

@elinor-fung elinor-fung merged commit 9399533 into dotnet:main Sep 30, 2024
88 of 90 checks passed
@elinor-fung elinor-fung deleted the assembly-debug-flags branch September 30, 2024 17:14
sirntar pushed a commit to sirntar/runtime that referenced this pull request Oct 3, 2024
…to Assembly (dotnet#107809)

This moves the initial computation into `Assembly` and removes the flags from `DomainAssembly`. Actual consumers were already getting the flags off of `Assembly` or `Module`
@am11
Copy link
Member

am11 commented Oct 5, 2024

@elinor-fung, I tried cleaning up the DomainAssembly class #108568, I'm not sure about EnumMemoryRegions in Assembly vs. DomainAssembly (just used the one in assembly which has slightly different ordering), but rest was straightforward. After this, DomainAssembly has just one field left; m_pAssembly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants