tree 95af5d26b08a32564dd51891df7d249302a5982a
parent f539c68ccd33ce140e5a15be3dcdbe4132d43948
author Tim Peters <tim.peters@gmail.com> 1018601570 +0000
committer Tim Peters <tim.peters@gmail.com> 1018601570 +0000
HG:extra convert_revision:svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/python/branches/legacy-trunk%4026349

_PyObject_DebugRealloc():  rewritten to let the underlying realloc do
most of the work.  In particular, if the underlying realloc is able to
grow the memory block in place, great (this routine used to do a fresh
malloc + memcpy every time a block grew).  BTW, I'm not so keen here on
avoiding possible quadratic-time realloc patterns as I am on making
the debug pymalloc more invisible (the more it uses memory "just like"
the underlying allocator, the better the chance that a suspected memory
corruption bug won't vanish when the debug malloc is turned on).