-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 DAC stack overflow in GetUsefulGlobals API #105366
Conversation
Tagging subscribers to this area: @tommcdon |
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.
Ack, sorry. Thanks.
We may need to backport this to preview 7 @tommcdon @mikem8361 if it's not too late |
@mikem8361 do our SOS tests hit this code path? Does this affect dump analysis, !analyze? What platforms/architectures are affected? |
The first thing SOS does for any command is to call this API. Yes, the SOS failed and !analyze will fail even with the new CLRMA code because it calls this API also. All platforms are affected. |
@leculver, this issue breaks SOS in .NET 9 preview 7. Do you think this is a blocking bug? |
/backport to release/9.0-preview7 |
Started backporting to release/9.0-preview7: https://github.com/dotnet/runtime/actions/runs/10253145361 |
I don't think this will break standard VS/WinDbg debugging. It will make all Watson/!analyze crashes useless, and it means we won't be able to solve any "real" bugs in Preview 7 if they come up. It's rare that we use Watson for a preview build, and it's rare to get a serious bug in preview that we need to debug via SOS. So, @tommcdon and folks, it's up to you to do that calculus... Either take this fix for P7, or not be able to debug any potential serious issue that requires SOS without a lot of work. (We can work around this if needed for a single crash dump, but it's time consuming and super annoying. We can't work around this for Watson/!analyze, they will need a fix or be broken for this preview.) |
A typo that caused stack recursion.