Repository navigation
Conversation
Member
Author
|
/azp-run runtime-interpreter |
|
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. |
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli |
Member
Author
|
/azp run runtime-interpreter |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Member
Author
|
/azp run runtime-interpreter |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Member
|
/azp run runtime-interpreter |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
A managed calli can enter the prestub and fail during compilation. The C++ exception is converted to managed SEH, but this call path was missing the SEH wrapper needed to reach interpreter catches. Adding the wrapper exposed missing personality routines on the interpreter call stubs: native unwinding left stale entries in the runtime frame chain (on windows, frames are popped explicitly in the SEH unwind handler, rather than relying on a destructor). Register the existing frame-chain cleanup handler on the Windows x64 and ARM64 call stubs.
Avoid using personality routines, pop frame explicitly in the prestub exception scenario Fix bug where we were clobbering callee saved register RSI and RDI.
* PreStubWorker needs to pop all explicit frames upto and including the PrestubMethodFrame * When propagating unhandled exception to the host, prevent it being caught and processed in the interpreter code.
BrzVlad
force-pushed
the
fix-clrinterp-seh
branch
from
October 30, 2026 09:26
5c3ceca to
2c245e0
Compare
Member
Author
|
/azp run runtime-interpreter |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Member
Author
|
/azp run runtime-interpreter |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
This branch has not been deployed
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
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.
A managed calli can enter the prestub and fail during compilation. The C++ exception is converted to managed SEH, but this call path was missing the SEH wrapper needed to reach interpreter catches.
Adding the wrapper exposed missing personality routines on the interpreter call stubs: native unwinding left stale entries in the runtime frame chain (on windows, frames are popped explicitly in the SEH unwind handler, rather than relying on a destructor). Register the existing frame-chain cleanup handler on the Windows x64 and ARM64 call stubs.