STINNER Victor <victor.stin...@gmail.com> added the comment:

"the bug should be fixed in all affected versions"

I don't understand why you insist to change Python 3.4 and Python 3.5. IMHO 
this issue only impacts OpenBSD.


"The current code in not correct on all platforms. We don't know how many of 
random bugs, hangs and crashes on other platforms are caused by this bug. I'm 
not surprised that it was caught on OpenBSD since the robustness and security 
of software is the goal of OpenBSD."

I'm not aware of these "random bugs, hangs and crashes on other platforms". Did 
you hear someone complaining about random crashes in Python?

We are running the Python suite multiple times per time on a large farm of 
buildbot workers. I  never saw the crashes that you mentionned.

IMHO it's very unlikely or impossible that _PyMem_DebugRawRealloc() erases 
bytes of a memory block that was just unallocated while another thread uses 
this new memory block for a new allocation. Most, if not all, calls to 
_PyMem_DebugRawRealloc() are protected by the GIL. If there is a single thread 
using the memory block, I think that it's perfectly fine to write after it's 
deallocated.

Well, maybe I'm plain wrong, and it's possible that shrinking a memory block 
makes the unallocator memory block really unaccessible, and that the memcpy() 
after the realloc() triggers a big crash. But I would like to *see* such crash 
to really be convinced :-)

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31626>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to