bpo-31626: Fix _PyMem_DebugRawRealloc() on OpenBSD #4119
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix memory debug hooks on OpenBSD: fix _PyMem_DebugRawRealloc().
Previously, the old resized memory block was modified after realloc()
success to fill now unused bytes with the DEADBYTE pattern. On
OpenBSD, modifying the old memory block causes a fatal error.
On OpenBSD, the function now erases the bytes before calling
realloc(), but keep a copy of erased bytes to restore them if
realloc() fails.
The behaviour on other platforms is unchanged: erased bytes after
realloc() success.
Co-Authored-By: Serhiy Storchaka storchaka@gmail.com
https://bugs.python.org/issue31626