Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: how do you know 'free' freed?
Keywords: free, malloc, memory, allocation
Message-ID: <11335@smoke.BRL.MIL>
Date: 19 Oct 89 09:48:56 GMT
References: <5521@hacgate.UUCP> <11275@smoke.BRL.MIL> <1175@svx.SV.DG.COM> <11313@smoke.BRL.MIL> <9762@attctc.Dallas.TX.US>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <9762@attctc.Dallas.TX.US> chasm@attctc.Dallas.TX.US (Charles Marslett) writes:
>If so, it also sounds like an excellent reason to disallow "buddy system"
>allocators.

Yes, and therefore you should complain loudly to the vendor that foists
one off on you.

Many BSD-based UNIX systems have a malloc() like this.  I don't like it
either.  The place to fix it, however, in in the C library, not in the
application.