[release/11.0] [cDAC] Export interpreter JIT manager descriptor - #134207
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Expose `ExecutionManager::m_pInterpreterJitManager` as the optional `InterpreterJitManagerAddress` cDAC data-descriptor global when CoreCLR is built with `FEATURE_INTERPRETER`. Will be used by #134072 for cDAC dump enumeration. Co-authored-by: Max Charlamb <maxcharlamb@microsoft.com> Copilot-Session: b507532c-3857-4e61-86a9-69fe22ec157b
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
steveisok
approved these changes
Sep 18, 2026
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli |
Member
The only shipping .NET 11 build with |
Member
No, iOS for cDAC is not a shipping scenario in 11. We can hold off on this change until 12. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #134190 to release/11.0
/cc @max-charlamb
Customer Impact
Without this descriptor, cDAC readers cannot discover the
InterpreterJitManagerdirectly. This prevents the reader work in #134072 from enumerating interpreter-owned code heaps, which can cause interpreter metadata to be omitted from dumps and prevent interpreter stack frames from being resolved correctly.The issue affects .NET 11 CoreCLR builds with
FEATURE_INTERPRETER.Regression
This is missing functionality required for the new .NET 11 interpreter and cDAC support, rather than a regression from previously supported behavior.
Testing
The change was validated by building CoreCLR with:
build.cmd clr.native /p:UseSharedCompilation=falseThe build completed with 0 warnings and 0 errors.
The corresponding reader implementation in #134072 also includes unit tests and a dump-based integration test using an interpreter-enabled process. The dump test verifies that cDAC can discover the interpreter JIT manager and enumerate its code heaps.
Risk
Low.
The change only adds an optional data-descriptor global under
FEATURE_INTERPRETER. It does not modify runtime behavior, object layout, or existing descriptor entries. Older readers ignore the additional global, while newer readers can use it to locate the existing process-wideInterpreterJitManager.IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging, notrelease/X.0.release/X.0(no-stagingsuffix).Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.