-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Add ExceptionDispatchInfo.SetRemoteStackTrace #50392
Add ExceptionDispatchInfo.SetRemoteStackTrace #50392
Conversation
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
Oh no what did I break? :( |
...braries/System.Private.CoreLib/src/System/Runtime/ExceptionServices/ExceptionDispatchInfo.cs
Outdated
Show resolved
Hide resolved
src/coreclr/System.Private.CoreLib/src/System/Exception.CoreCLR.cs
Outdated
Show resolved
Hide resolved
src/coreclr/System.Private.CoreLib/src/System/Exception.CoreCLR.cs
Outdated
Show resolved
Hide resolved
src/coreclr/System.Private.CoreLib/src/System/Exception.CoreCLR.cs
Outdated
Show resolved
Hide resolved
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.
Other than Jan's comments, LGTM.
- Share more code across coreclr + mono
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!
Opened #50520 to track the crossgen2 test failures. |
Resolves #50044.
The approved API (see #50044 (comment)) returns
bool
, which is clearly a mistake given that we wanted to make it a non-try method just like its sibling SetCurrentStackTrace. So for this PR, I made the method returnException
, just like its sibling. I believe this follows the spirit of what the API review intended.It's too difficult for me to test the "immutable agile exception" case, so I didn't. That's going to have to remain within the purview of code review.
Also took this time to do some minor cleanup of existing devdoc and unit tests. Nothing too fancy.
/cc @ReubenBond