Newsgroups: comp.os.msdos.djgpp
Date: Tue, 3 Jul 2001 00:47:33 +0100 (BST)
From: Daniel Barker <sokal AT holyrood DOT ed DOT ac DOT uk>
To: <djgpp AT delorie DOT com>
Subject: Re: malloc() problem, DJDEV 203
In-Reply-To: <200107022219.SAA04299@envy.delorie.com>
Message-ID: <Pine.SOL.4.33.0107030043180.14632-100000@holyrood.ed.ac.uk>
References: <Pine DOT SOL DOT 4 DOT 33 DOT 0107022250120 DOT 27631-100000 AT holyrood DOT ed DOT ac DOT uk>
 <200107022219 DOT SAA04299 AT envy DOT delorie DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Mon, 2 Jul 2001, DJ Delorie wrote:

[snip]

> It would be trivial to add a check for values 4294967289U through
> 4294967295U in djgpp's src/libc/ansi/stdlib/malloc.c if someone wants
> to use this as an excuse to get into djgpp development ;-)

Thank you for the explanation.

Alternatively, DJGPP malloc() could be changed to return NULL for
zero-byte allocations. This is a significant change of behaviour but is
allowed by the C standard.

-- 
Daniel Barker.