Uh oh!
There was an error while loading. Please reload this page.
release/6.0.1: Preserve last error in call-counting stubs - #60887
Merged
Conversation
kouvel
approved these changes
Oct 26, 2021
jeffschwMSFT
approved these changes
Oct 26, 2021
jeffschwMSFT
left a comment
Member
There was a problem hiding this comment.
Approved. We will take for consideration in .NET 6 servicing
Anipik
commented
Nov 10, 2021
Contributor
/azp run runtime, runtime-dev-innerloop, dotnet-linker-test |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Anipik
commented
Nov 11, 2021
Contributor
/azp run runtime, runtime-dev-innerloop, dotnet-linker-tests |
|
Azure Pipelines successfully started running 3 pipeline(s). |
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Backport of #60886 to release/6.0
/cc @jkotas
Customer Impact
Intermittent corruption of error code returned by
Marshal.GetLastSystemError/GetLastPInvokeErrorAPIs . This bug can manifest itself as a wrong exception being thrown, or as a bogus exception being thrown when PInvoke succeed. The bug manifested itself at least 3 times in dotnet/runtime CI in last month.Testing
No reliable repro, fix verified by stepping through the code in debugger.
Risk
Low.