[cDAC] Properly handle reportInteropMD special case

[max-charlamb]

Resolves #119724

[Copilot]

Pull Request Overview

This PR implements proper handling of the special reportInteropMD case in the cDAC stack walking functionality, resolving issue #119724. The implementation adds logic to detect when an InlinedCallFrame should report the actual interop MethodDesc instead of the standard frame MethodDesc.

• Adds detection logic for the reportInteropMD special case based on frame type, stack walk state, and method characteristics
• Implements new helper methods to support interop method detection and return address retrieval
• Updates documentation to explain the special case handling and API differences

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
ClrDataFrame.cs	Refactors legacy implementation error handling and adds debug assertion for result comparison
StackWalk_1.cs	Implements the main reportInteropMD detection and handling logic in GetMethodDescPtr
FrameIterator.cs	Adds helper methods for frame type checking and return address retrieval
RuntimeTypeSystem_1.cs	Adds IL stub type detection and MDContext argument checking functionality
IRuntimeTypeSystem.cs	Adds interface method for checking MDContext arguments
StackWalk.md	Documents the special case handling in the API specification
RuntimeTypeSystem.md	Documents the new HasMDContextArg method and related enumerations

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[rcj1]

LGTM besides the one comment