Date: Mon, 22 Sep 1997 01:51:28 +0200 From: Eivind Eklund <eivind@bitbox.follo.net> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Nate Williams <nate@mt.sri.com>, Eivind Eklund <perhaps@yes.no>, phk@critter.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Message-ID: <19970922015128.32876@bitbox.follo.net> In-Reply-To: <24205.874885838@time.cdrom.com>; from Jordan K. Hubbard on Sun, Sep 21, 1997 at 04:50:38PM -0700 References: <19970922005506.48602@bitbox.follo.net> <24205.874885838@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 21, 1997 at 04:50:38PM -0700, Jordan K. Hubbard wrote: > > It doesn't. However, it has a formulation that IMHO is too > > restrictive - that free() 'makes the memory available for further use > > by the program' (from memory). Thus, an implementation of > > Bizarre, are you sure? That's exactly 180 degrees counter to what > I've always learned about storage allocators: If you count on free() > to not corrupt the data you pass to it, you deserve to lose and lose > big. My typo. I mean 'further allocation'. Eivind.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970922015128.32876>