Skip to content

mono_get_generic_info_from_stack_frame fix for default interface methods - #64566

Merged
lambdageek merged 1 commit into
dotnet:mainfrom
Unity-Technologies:dotnet-upstream/issue-62334
Feb 4, 2022
Merged

mono_get_generic_info_from_stack_frame fix for default interface methods#64566
lambdageek merged 1 commit into
dotnet:mainfrom
Unity-Technologies:dotnet-upstream/issue-62334

Conversation

@bholmes

Copy link
Copy Markdown
Contributor

The context is a MonoMethodRuntimeGenericContext when the method is a
default interface method.

Also re-enable broken DIM tests.

Fixes dotnet/runtime #62334

The context is a MonoMethodRuntimeGenericContext when the method is a
default interface method.
Also re-enable broken DIM tests.
Fixes dotnet/runtime dotnet#62334
@ghostghost added area-VM-meta-mono community-contribution Indicates that the PR has been added by a community member labels Jan 31, 2022
@bholmes

Copy link
Copy Markdown
ContributorAuthor

Later in mono_get_generic_context_from_stack_frame the code is treating the info address as a MonoMethodRuntimeGenericContext . This PR ensures that mono_get_generic_info_from_stack_frame assigns the info value consistently.

https://github.com/dotnet/runtime/pull/60770/files#diff-6058d387fb779d535bf433950cc6a61392cdf99bf5174c278f195487715cdeb0R843-R849

@bholmes

Copy link
Copy Markdown
ContributorAuthor

If approved will need to update the Mono PR as well. mono/mono#21356

@lambdageeklambdageek self-assigned this Feb 1, 2022
@lambdageek
lambdageek merged commit 9055c8b into dotnet:mainFeb 4, 2022
thaystg added a commit to thaystg/runtime that referenced this pull request Feb 17, 2022
@ghostghost locked as resolved and limited conversation to collaborators Mar 6, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-VM-meta-monocommunity-contributionIndicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@bholmes@vargaz@lambdageek