-
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
Test failure in Interop workitem: Assert failure !"About to FailFast. set DOTNET_AssertOnFailFast=0 if this is expected" #99133
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsBuild: https://dev.azure.com/dnceng-public/public/_build/results?buildId=578823&view=results Error message:
|
@jakobbotsch PTAL. |
This is unrelated issue. The GSCookie address computed during stackwalking is off by 4. It is off by 4 because the stack pointer is off by 4. The stack pointer is off by 4 because a bug introduced by #57244. The change missed updating The bug is harmless most of time since stack pointer is not typically used for anything crucial during unwinding of methods with calli. The JIT stress triggered the crash by creating atypical variant of the code where stack pointer ended up being used to compute the GSCookie address. |
Bug introduced by dotnet#57244 Fixes dotnet#99133
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=578823&view=results
Build error leg or test failing: coreclr windows x86 Checked jitstress_random_2 @ Windows.10.Amd64.Open
Error message:
The text was updated successfully, but these errors were encountered: