[release/5.0] Port Debugger data breakpoint deadlock fixes to .NET 5.0#44563
[release/5.0] Port Debugger data breakpoint deadlock fixes to .NET 5.0#44563sdmaclea merged 2 commits intodotnet:release/5.0from
Conversation
* Add ICorDebugHeapValue4 * Add EnableGCNotificationEvents deprecation comment
…otnet#44549) * Stop providing IID_ICorDebugProcess10 Prevent older VS versions from setting managed data breakpoints. * Simplify the thread collision logic to prevent deadlock This is a simplification of dotnet#44539 as proposed by @kouvel
|
Tagging subscribers to this area: @tommcdon DetailsIssue meta data
|
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jeffschwMSFT
left a comment
There was a problem hiding this comment.
Approved. Please get several code reviews as the change is on the larger side.
|
Sure. I might have neglected to mention that a lot of this is machine generated core from the MIDL compiler. I left the whitespace as MIDL generated it. The change set looks substantially smaller with ignore whitespace. |
|
Marking servicing approved per tactics |
Backport of #44471 & #44549 to release/5.0
Customer Impact
Regression?
Testing
Risk
This is a minimal risk patch.
CC @tommcdon @noahfalk @kouvel @chuckries @jeffschwMSFT