Detect Py_TRACE_REFS at runtime and calculate object offsets accordingly #1426
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lostmsu
force-pushed
the
bugs/Py_DEBUG
branch
2 times, most recently
from
de42b75
to
689f0d8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
What does this implement/fix? Explain your changes.
This gets rid of
#if PYTHON_WITH_PYDEBUGby detecting if objects have reference tracing (e.g.Py_TRACE_REFS) enabled at runtime based on the offset of refcount field in a new object.Does this close any currently open issues?
It should fix #1412
Any other comments?
Slight refactoring had to be done to ensure initialization code does not depend on knowing field offsets until they actually become available.