[Python-Dev] Malloc interface (was: [Patches] Re: Garbage collection patches for Python (fwd)

Tim Peters tim_one@email.msn.com
Sun, 13 Feb 2000 02:44:55 -0500


[Vladimir Marangozov]
> ...
> In order to pave the way for alternatives to libc's malloc, we must
> propose a clean solution. Hence it would be good to collect as much
> opinions/reactions on the subject as possible and settle on an
> interface which would be convenient for everybody.

I can't imagine a rational *objection* to cleaning this stuff up.

BTW, at work we bumped into a horrible problem with malloc under Linux:
Linux "overcommits", meaning that malloc may return success, yet subsequent
reference to the malloc'ed memory may segfault!  Absolutely sucks, and the
Linux developers aren't inclined to fix it (they made an analogy to
overbooking plane flights -- even MS wouldn't be so lame <wink>).  This
showed up on a "small platform" project, where swap space was so small as to
be essentially not there.

For that and a gazillion other reasons, I (like you) would be much happier
if it were easy to plug in a malloc replacement, and I agree that requires
reworking of the current code.

just-do-it-ly y'rs  - tim