➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients davin, larry, serhiy.storchaka, vstinner
Date 2017-10-01.13:02:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506862951.0.0.213398074469.issue31626@psf.upfronthosting.co.za>
In-reply-to
Content 
Using nested _PyMem_DebugRawRealloc() looks suspicions to me. This may be a bug.

But even without nested _PyMem_DebugRawRealloc() writing to the extra memory after using realloc() looks wrong to me. This can break other non-trivial system allocators which write an information past the allocated block. This can cause a segfault if unused memory pages are returned to OS.

After creating the PR I have found that it literally restores the code of 2.7 and 3.3. 3.4 and later contain this bug. The bug looks enough serious to me for fixing it in 3.4 and 3.5.
History
Date User Action Args
2017-10-01 13:02:31serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, larry, davin
2017-10-01 13:02:31serhiy.storchakasetmessageid: <1506862951.0.0.213398074469.issue31626@psf.upfronthosting.co.za>
2017-10-01 13:02:30serhiy.storchakalinkissue31626 messages
2017-10-01 13:02:30serhiy.storchakacreate