From owner-freebsd-hackers Sun Sep 21 16:51:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25545 for hackers-outgoing; Sun, 21 Sep 1997 16:51:46 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25535 for ; Sun, 21 Sep 1997 16:51:37 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA24215; Mon, 22 Sep 1997 01:51:29 +0200 (MET DST) Message-ID: <19970922015128.32876@bitbox.follo.net> Date: Mon, 22 Sep 1997 01:51:28 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: Nate Williams , Eivind Eklund , phk@critter.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) References: <19970922005506.48602@bitbox.follo.net> <24205.874885838@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <24205.874885838@time.cdrom.com>; from Jordan K. Hubbard on Sun, Sep 21, 1997 at 04:50:38PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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.