[release/8.0] [Mono] Fix unsafe accessor related issue for full AOT #91270
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 #91216 to release/8.0
/cc @fanyang-mono
Customer Impact
Prior to this PR, the customer might hit an assertion or a SIGSEGV, when using UnsafeAccessor with full AOT. This PR fixes those issues by
WRAPPER_SUBTYPE_UNSAFE_ACCESSOR
member_name
is not NULLTesting
Local testing:
UnsafeAccessorsTests.dll
encountered an assertion:UnsafeAccessorsTests.dll
finished without error:Risk
Low risk.