-
Couldn't load subscription status.
- Fork 5.2k
Avoid reporting incorrect thread context to Watson #117522
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
Conversation
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.
Pull Request Overview
This PR prevents Watson from receiving an incorrect thread context when RaiseFailFastException is invoked for fatal errors.
- Adds a boolean flag to detect fatal-error contexts.
- Updates the
ContextRecordargument inRaiseFailFastExceptionto passNULLwhen the flag is set.
Comments suppressed due to low confidence (1)
src/coreclr/vm/excep.cpp:3570
- [nitpick] Consider renaming
fAvoidReportContextToRaiseFailFastto a shorter, more descriptive name (e.g.fSkipContextReportorskipContextForFatalError) to improve readability.
bool fAvoidReportContextToRaiseFailFast = tore.IsFatalError(); // avoid reporting incorrect thread context to Watson
|
Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag |
|
We had to play games with context passed to Watson on win x86 - see dotnet/coreclr#23289 . You may want to double check that Watson and dump debugging on win x86 works well with this change. |
Verified |
Fixes #111182
This change avoids reporting contexts generated from EEPolicy::HandleFatalError to Watson