Issue #2620: Overflow checking when allocating or reallocating memory
commit7989285370324cc53ac6e6e82769578a2e98b0ed
authorgregory.p.smith <gregory.p.smith@6015fed2-1504-0410-9fe1-9d1591cc4771>
Tue, 22 Jul 2008 04:46:32 +0000 (22 04:46 +0000)
committergregory.p.smith <gregory.p.smith@6015fed2-1504-0410-9fe1-9d1591cc4771>
Tue, 22 Jul 2008 04:46:32 +0000 (22 04:46 +0000)
tree6f9938031ae92cf762ed76c56e5e01e70e61961b
parent67cefc65d1b603ffbb5b829196e05fd899ec6f4c
Issue #2620: Overflow checking when allocating or reallocating memory
was not always being done properly in some python types and extension
modules.  PyMem_MALLOC, PyMem_REALLOC, PyMem_NEW and PyMem_RESIZE have
all been updated to perform better checks and places in the code that
would previously leak memory on the error path when such an allocation
failed have been fixed.

git-svn-id: http://svn.python.org/projects/python/trunk@65182 6015fed2-1504-0410-9fe1-9d1591cc4771
Doc/c-api/memory.rst
Include/pymem.h
Misc/NEWS
Modules/almodule.c
Modules/arraymodule.c
Modules/selectmodule.c
Objects/obmalloc.c