Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!texbell!attctc!chasm
From: chasm@attctc.Dallas.TX.US (Charles Marslett)
Newsgroups: comp.lang.c
Subject: Re: how do you know 'free' freed?
Summary: ???
Keywords: free, malloc, memory, allocation
Message-ID: <9762@attctc.Dallas.TX.US>
Date: 18 Oct 89 13:21:31 GMT
References: <5521@hacgate.UUCP> <11275@smoke.BRL.MIL> <1175@svx.SV.DG.COM> <11313@smoke.BRL.MIL>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 20

In article <11313@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
.. In article <1175@svx.SV.DG.COM> gary@svx.SV.DG.COM () writes:
.. >The correct answer is "malloc/free is somewhat broken in Sunos 4.0.1-3".
.. >This has been mentioned before, in a Feb. Sun Spots article - here it is...
.. 
.. That sounds more like a "buddy system" allocator working normally.

If so, it also sounds like an excellent reason to disallow "buddy system"
allocators.

The purpose of malloc/calloc/et al. is to keep us from worrying about this
stuff -- if the allocator throws us traps, it better be easily bypassed.

Charles
===============================================================================
"Those who would sacrifice **  Charles Marslett
liberty for security,      **  STB Systems, Inc. <-- apply all std. disclaimers
deserve neither."          **  Wordmark Systems  <-- that's just me
  -- Benjamin Franklin     **  chasm\@attctc.dallas.tx.us
-------------------------------------------------------------------------------