bpo-9263: Fix _PyObject_Dump() for freed object by vstinner · Pull Request #10661 · python/cpython (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation1 Commits1 Checks0 Files changed
Conversation
This file contains hidden or 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
[ Show hidden characters]({{ revealButtonHref }})
If _PyObject_Dump() detects that the object is freed, don't try to
dump it (exit immediately).
Enhance also _PyObject_IsFreed(): it now detects if the pointer
itself looks like freed memory.
https://bugs.python.org/issue9263
If _PyObject_Dump() detects that the object is freed, don't try to dump it (exit immediately).
Enhance also _PyObject_IsFreed(): it now detects if the pointer itself looks like freed memory.
@vstinner: Please replace # with GH- in the commit message next time. Thanks!
vstinner added a commit that referenced this pull request
_PyObject_Dump() now uses an heuristic to check if the object memory has been freed: log "" in that case.
The heuristic rely on the debug hooks on Python memory allocators which fills the memory with DEADBYTE (0xDB) when memory is deallocated. Use PYTHONMALLOC=debug to always enable these debug hooks.
(cherry picked from commit 82af0b6)
If _PyObject_Dump() detects that the object is freed, don't try to dump it (exit immediately).
Enhance also _PyObject_IsFreed(): it now detects if the pointer itself looks like freed memory.
(cherry picked from commit 2cf5d32)
vstinner added a commit that referenced this pull request
_PyObject_Dump() now uses an heuristic to check if the object memory has been freed: log "" in that case.
The heuristic rely on the debug hooks on Python memory allocators which fills the memory with DEADBYTE (0xDB) when memory is deallocated. Use PYTHONMALLOC=debug to always enable these debug hooks.
(cherry picked from commit 82af0b6)
If _PyObject_Dump() detects that the object is freed, don't try to dump it (exit immediately).
Enhance also _PyObject_IsFreed(): it now detects if the pointer itself looks like freed memory.
(cherry picked from commit 2cf5d32) (cherry picked from commit 95036ea)