-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix NativeAOT unhandled exception stack trace #91415
Fix NativeAOT unhandled exception stack trace #91415
Conversation
The recent change to add a new exception handling mechanism to coreclr has broken stack traces on unhandled exceptions in nativeaot. This change fixes it by reverting the part of the change that caused the problem and that turned out to not to be needed for the new exception handling either. Close dotnet#91298
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsThe recent change to add a new exception handling mechanism to coreclr has broken stack traces on unhandled exceptions in nativeaot. This change fixes it by reverting the part of the change that caused the problem and that turned out to not to be needed for the new exception handling either. Close #91298
|
Should we add a smoke test for this? |
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.
Thanks!
I think a regular test - that runs on all runtime flavors - would be enough. |
Ok, let me add a test here. |
The test needs fixes for Mono (Mono uses different exit code and different formatting of the output). |
df6b500
to
d9defde
Compare
d9defde
to
f148f79
Compare
Thank you! |
The recent change to add a new exception handling mechanism to coreclr has broken stack traces on unhandled exceptions in nativeaot.
This change fixes it by reverting the part of the change that caused the problem and that turned out to not to be needed for the new exception handling either.
Close #91298