Skip to content

gh-111178: Fix PyRangeIter_Type deallocator #131162

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

Merged
merged 1 commit into from
Mar 13, 2025
Merged

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Mar 12, 2025

Don't use PyObject_Free() as tp_dealloc to avoid an undefined behavior. Instead, use the default deallocator which just calls tp_free which is PyObject_Free().

Don't use PyObject_Free() as tp_dealloc to avoid an undefined
behavior. Instead, use the default deallocator which just calls
tp_free which is PyObject_Free().
@vstinner vstinner merged commit 0c6c52f into python:main Mar 13, 2025
45 checks passed
@vstinner vstinner deleted the ubsan_range3 branch March 13, 2025 09:46
plashchynski pushed a commit to plashchynski/cpython that referenced this pull request Mar 17, 2025
Don't use PyObject_Free() as tp_dealloc to avoid an undefined
behavior. Instead, use the default deallocator which just calls
tp_free which is PyObject_Free().
seehwan pushed a commit to seehwan/cpython that referenced this pull request Apr 16, 2025
Don't use PyObject_Free() as tp_dealloc to avoid an undefined
behavior. Instead, use the default deallocator which just calls
tp_free which is PyObject_Free().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant