From owner-freebsd-hackers  Mon Feb 26  9:23:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guild.plethora.net (guild.plethora.net [205.166.146.8])
	by hub.freebsd.org (Postfix) with ESMTP id 29C9C37B4EC
	for <freebsd-hackers@freebsd.org>; Mon, 26 Feb 2001 09:23:08 -0800 (PST)
	(envelope-from seebs@guild.plethora.net)
Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1])
	by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f1QHN6613015
	for <freebsd-hackers@freebsd.org>; Mon, 26 Feb 2001 11:23:07 -0600 (CST)
Message-Id: <200102261723.f1QHN6613015@guild.plethora.net>
From: seebs@plethora.net (Peter Seebach)
Reply-To: seebs@plethora.net (Peter Seebach)
To: freebsd-hackers@freebsd.org
Subject: Re: Setting memory allocators for library functions. 
In-reply-to: Your message of "Mon, 26 Feb 2001 10:19:01 MST."
             <15002.36869.925599.285850@nomad.yogotech.com> 
Date: Mon, 26 Feb 2001 11:23:06 -0600
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <15002.36869.925599.285850@nomad.yogotech.com>, Nate Williams writes
:
>Even in this case, there's no way to prove your code is not going to
>crash.

Sure.  But you can at least prove that all crashes are the result of bugs,
not merely design "features".  From the point of view of proving that a
system is designed correctly, memory overcommit is a "bug".  ;)

-s

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message