[Tim, on PyMem vs PyObject memory mismatches]
> ... Alas, in a release(*) build, Python's test suite segfaulted all over the
> place.
>
> So far I found one smoking gun: in _subprocess.c, ...
And Python's front end was chock full o' these, sometimes even getting
memory via PyMem and releasing it via PyObject.
I checked the change in, under the theory that there's never going to
be a better time to clean up this mess. As the checkin comment says,
If extension modules in real life prove as sloppy as Python's
front end, we'll have to revert the objimpl.h + pymem.h part of this
patch. Note that no problems will show up in a debug build (all
calls still go thru obmalloc then). Problems will show up only in a
release build, most likely segfaults.
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
