-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Add ICorDebugHeapValue4 -- CreatePinnedHandle #44471
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.
Otherwise LGTM
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
b33db21
to
a122ca3
Compare
Thanks @sdmaclea! LGTM, though I'm not too familiar with adding APIs in this area. |
Tagging subscribers to this area: @tommcdon Issue meta data
|
@kouvel I expect when you have the rest of the tiered JIT, data breakpoint deadlock fix finished. You will backport the whole fix to 5.0 servicing branch. |
Yep about to put up a PR for my side shortly, will port both once that's in |
* Add ICorDebugHeapValue4 * Add EnableGCNotificationEvents deprecation comment
#44563) * Add ICorDebugHeapValue4 -- CreatePinnedHandle (#44471) * Add ICorDebugHeapValue4 * Add EnableGCNotificationEvents deprecation comment * Drop support for IID_ICorDebugProcess10 and fix thread suspend logic (#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 #44539 as proposed by @kouvel
No description provided.