GH-146527: Add get_gc_stats function to _remote_debugging#148071
Conversation
|
I'm not sure about news entry too. |
Sorry, something went wrong.
a929c0c to
e95d13d
Compare
May 2, 2026 13:41
|
Thanks a lot for the great work on this @sergey-miryanov! I pushed a set of follow-up commits on top because we are getting close to beta freeze and I wanted to make sure this lands in a solid shape. The follow-ups validate the remote GC stats offset and reject incompatible remote layoutsinstead of accepting short reads, reject a NULL remote GC stats pointer, record timestamps in the free-threaded GC path, and document why On the test side, I renamed the test file to |
Sorry, something went wrong.
Documentation build overview
4 files changed± contents.html± c-api/perfmaps.html± whatsnew/3.15.html± whatsnew/changelog.html |
Sorry, something went wrong.
pablogsal
left a comment
There was a problem hiding this comment.
LGTM
Thanks for this @sergey-miryanov this was such a cool idea!
Sorry, something went wrong.
39f123c
into
python:main
May 2, 2026
|
Thanks so much, @pablogsal! You did excellent work shaping this into its final form! |
Sorry, something went wrong.
This PR implements second part of the issue. Instead of adding a new module or extending the
gcmodule we add new function to the_remote_debuggingmodule as it is a best place for this.