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 vstinner
Recipients davin, larry, serhiy.storchaka, vstinner
Date 2017-10-25.14:18:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"I tried to build CPython on 64-bit OpenBSD. It was built successfully, but tests crash."

It's the first time that anyone complains about _PyMem_DebugRawRealloc(). The behaviour seems to be very specific to OpenBSD.

Even if the current code is "weird", it works very well and is effecient.

I proposed attached PR 4119 which makes _PyMem_DebugRawRealloc() behaves correctly: erase bytes *before* calling realloc(), but keeps a copy if realloc() fails. My PR only changes the behaviour on OpenBSD. It keeps the current behaviour (erase bytes *after* realloc, if realloc succeeded) on other platforms for performance reasons.
Date User Action Args
2017-10-25 14:18:51vstinnersetrecipients: + vstinner, larry, serhiy.storchaka, davin
2017-10-25 14:18:51vstinnersetmessageid: <>
2017-10-25 14:18:51vstinnerlinkissue31626 messages
2017-10-25 14:18:51vstinnercreate