From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <2ba96fc2203d0c710f6da96b72127752@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Tue,  4 Sep 2007 10:41:33 -0400
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 overcommits memory?
In-Reply-To: <3e1162e60709040639u39e8ee90o42e71103aa1ce2ab@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: b79597a4-ead2-11e9-9d60-3106f5b1d025

On Tue Sep  4 09:39:37 EDT 2007, leimy2k@gmail.com wrote:

> Yep, I've seen code with totally erroneous use of realloc work perfectly on
> Linux for example, due to it's behavior.  Then I built it on FreeBSD and it
> failed appropriately :-).

what does this have to do with memory overcommitment?  k&r second ed,
p. 252 specifies that malloc and realloc return NULL if the request can't
be specified.

- erik