| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
3.8 is in security-fix-only mode; adjusting the backport labels. |
Sorry, something went wrong.
|
Yes, this showed up for me because I introduced a new path that, for exponent 1 and no modulus, invoked REDUCE but not MULT. Without a modulus, REDUCE didn't overwrite temp, and without MULT nothing else did either. Nasty 😉. |
Sorry, something went wrong.
There was a problem hiding this comment.
Ship it!
Sorry, something went wrong.
|
Thanks @mdickinson for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.9. |
Sorry, something went wrong.
|
Sorry @mdickinson, I had trouble checking out the 3.10 backport branch. |
Sorry, something went wrong.
|
GH-26702 is a backport of this pull request to the 3.9 branch. |
Sorry, something went wrong.
(cherry picked from commit 5924243) Co-authored-by: Mark Dickinson <mdickinson@enthought.com>
|
GH-26703 is a backport of this pull request to the 3.10 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR fixes a reference counting bug introduced in #13266 and identified by @tim-one in #26662: if we don't set temp to NULL, and if the value it has at this point is retained until the end of the function, then we end up doing an extra decref. I spent some time trying to identify a test-case that exercises this bug, and failed - I couldn't find a code path where temp isn't re-used at some point. Nevertheless, it's a potential point of fragility for maintenance of this code.
https://bugs.python.org/issue36027