-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
asserting that the tstate pointer is non-NULL using assert #122928
Comments
As mentioned in the PR, a With that being said, calling |
My understanding is that a problematic dangling pointer could be caused by the legacy non-isolated subinterpreter created with See also #109794 (comment), #104341 (comment). |
I'm wondering whether the issue should still mention dangling pointer since a dangling pointer is a valid pointer (hence non-null) pointing to invalid memory. It's more about asserting that the pointer is non-NULL using |
Please change the title, or make the PR belong to gh-109793. The current title is not good for closing here as "completed". |
The change is not needed: #122929 (review) |
Bug report
Bug description:
https://github.com/python/cpython/blob/main/Python/pystate.c#L3016
To prevent dangling pointer issues, adding a check for NULL ensures that invalid pointers are not dereferenced
Linked PRs
The text was updated successfully, but these errors were encountered: