-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Cleanup some dead paths in EH #122852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup some dead paths in EH #122852
Conversation
|
Tagging subscribers to this area: @mangod9 |
|
The test failure looks related: |
fd79a0b to
06ce69d
Compare
|
Could you please resolve the conflict? |
src/coreclr/System.Private.CoreLib/src/System/Threading/Thread.CoreCLR.cs
Outdated
Show resolved
Hide resolved
jkotas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
@janvorli Could you please take a look as well?
|
I will take a look. |
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
janvorli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/ba-g infrastructure timeout (job running for 11 hours) |
Also moves
ThreadStartExceptionto managed code.The general question is about where
RaiseExceptionis required instead ofDispatchManagedException. I played a bit with it in QCall andDispatchManagedExceptionseems to interop directly with C++ EH on Windows.UnwindAndContinueRethrowHelperAfterCatch(nativeRethrow)is intentional, butHandleThreadAbortdoesn't look like.