From owner-freebsd-hackers  Sun Sep 21 16:51:07 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA25515
          for hackers-outgoing; Sun, 21 Sep 1997 16:51:07 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25507
          for <hackers@FreeBSD.ORG>; Sun, 21 Sep 1997 16:50:58 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA24213; Sun, 21 Sep 1997 16:50:40 -0700 (PDT)
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?) 
In-reply-to: Your message of "Mon, 22 Sep 1997 00:55:06 +0200."
             <19970922005506.48602@bitbox.follo.net> 
Date: Sun, 21 Sep 1997 16:50:38 -0700
Message-ID: <24205.874885838@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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