Date: Sun, 21 Sep 1997 16:50:38 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Eivind Eklund <eivind@bitbox.follo.net> 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: <24205.874885838@time.cdrom.com> In-Reply-To: Your message of "Mon, 22 Sep 1997 00:55:06 %2B0200." <19970922005506.48602@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24205.874885838>