Fix EH transition on native to interpreted boundary#120378
Merged
janvorli merged 2 commits intodotnet:mainfrom Oct 7, 2025
Merged
Fix EH transition on native to interpreted boundary#120378janvorli merged 2 commits intodotnet:mainfrom
janvorli merged 2 commits intodotnet:mainfrom
Conversation
There is a case where an interpreted code is called by CallDescrWorker and the code that called the CallDescrWorker was invoked via pinvoke. In that case, the SfiNextWorker was not detecting that the exception propagates to CallDescrWorker due to the fact that the final StackFrameIterator::GetFrameState() was returning SFITER_FRAME_FUNCTION for the next pinvoke and not reporting any intermediate SFITER_NATIVE_MARKER_FRAME.
Contributor
|
Tagging subscribers to this area: @BrzVlad, @janvorli, @kg |
davidwrighton
approved these changes
Oct 3, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There is a case where an interpreted code is called by CallDescrWorker and the code that called the CallDescrWorker was invoked via pinvoke. In that case, the SfiNextWorker was not detecting that the exception propagates to CallDescrWorker due to the fact that the final StackFrameIterator::GetFrameState() was returning SFITER_FRAME_FUNCTION for the next pinvoke and not reporting any intermediate SFITER_NATIVE_MARKER_FRAME.