[issue32584] Uninitialized free_extra in code_dealloc

Irit Katriel added the comment: Is there anything left to do on this issue? It seems like a question more than a bug report. -- nosy: +iritkatriel ___ Python tracker ___

[issue32584] Uninitialized free_extra in code_dealloc

Brett Cannon added the comment: co_extra_freefuncs is an array of pointers, so there's no way for it to be uninitialized unless you didn't initialize the interpreter state (https://github.com/python/cpython/blob/b193fa996a746111252156f11fb14c12fd6267e6/Include/pystate.h#L155). And looking

[issue32584] Uninitialized free_extra in code_dealloc

Change by Brett Cannon : -- nosy: +dino.viehland ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32584] Uninitialized free_extra in code_dealloc

Change by Serhiy Storchaka : -- nosy: +brett.cannon priority: normal -> high versions: +Python 3.6, Python 3.8 ___ Python tracker ___

[issue32584] Uninitialized free_extra in code_dealloc

New submission from Jeethu Rao : In one of patches I'm building, (yet another attempt at caching LOAD_GLOBALS)[1], I'm using the private APIs from PEP 523 to store an array with every code object. I'm calling _PyEval_RequestCodeExtraIndex with PyMem_Free for the freefunc