summaryrefslogtreecommitdiffstats
path: root/Python/gc_free_threading.c
diff options
context:
space:
mode:
authorSam Gross <colesbury@gmail.com>2024-01-16 21:42:15 (GMT)
committerGitHub <noreply@github.com>2024-01-16 21:42:15 (GMT)
commitb331381485c1965d1c88b7aee7ae9604aca05758 (patch)
tree17595ab4ee790ebb042c5a9661848623fb79076e /Python/gc_free_threading.c
parentc86571e4c9765a88ba05a7d9b874b40af0e1d6ab (diff)
downloadcpython-b331381485c1965d1c88b7aee7ae9604aca05758.zip
cpython-b331381485c1965d1c88b7aee7ae9604aca05758.tar.gz
cpython-b331381485c1965d1c88b7aee7ae9604aca05758.tar.bz2
gh-112529: Track if debug allocator is used as underlying allocator (#113747)
* gh-112529: Track if debug allocator is used as underlying allocator The GC implementation for free-threaded builds will need to accurately detect if the debug allocator is used because it affects the offset of the Python object from the beginning of the memory allocation. The current implementation of `_PyMem_DebugEnabled` only considers if the debug allocator is the outer-most allocator; it doesn't handle the case of "hooks" like tracemalloc being used on top of the debug allocator. This change enables more accurate detection of the debug allocator by tracking when debug hooks are enabled. * Simplify _PyMem_DebugEnabled
Diffstat (limited to 'Python/gc_free_threading.c')
0 files changed, 0 insertions, 0 deletions