[issue31626] Writing in freed memory in _PyMem_DebugRawRealloc() after shrinking a memory block
Serhiy Storchaka
report at bugs.python.org
Fri Nov 24 06:57:24 EST 2017
Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:
> * 3.6: don't memset() --> correct, but don't detect "use after free" bug
> when a memory block is skrinked
And doesn't detect "use after free" bug when a memory block is expanded. And
2.7 doesn't detect this. Only 3.7 detects this.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31626>
_______________________________________
More information about the Python-bugs-list
mailing list