Newsgroups:	comp.os.msdos.djgpp
Date:	Fri, 6 Jul 2001 01:12:27 +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:	<200107030107.VAA05731@envy.delorie.com>
Message-ID:	<Pine.SOL.4.33.0107060107100.29532-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> <Pine DOT SOL DOT 4 DOT 33 DOT 0107030043180 DOT 14632-100000 AT holyrood DOT ed DOT ac DOT uk>
	<200107022351 DOT TAA05124 AT envy DOT delorie DOT com> <Pine DOT SOL DOT 4 DOT 33 DOT 0107030132070 DOT 19125-100000 AT holyrood DOT ed DOT ac DOT uk>
	<200107030107 DOT VAA05731 AT envy DOT delorie DOT com>
MIME-Version:	1.0
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

On Mon, 2 Jul 2001, DJ Delorie wrote:

> I wouldn't trust any request bigger than 2G, because you never know
> when the OS is going to treat the number like a signed number.  sbrk()
> is the interface to the OS; has anyone tried testing that
> independently of malloc?  And has anyone tried testing GNU malloc to
> see if it has the same problems?

How about if DJGPP malloc() always returned NULL (without even trying) for
any allocation request exceeding n bytes, where n is the size of the
largest dynamic array one can ever get with DOS/DPMI?

This would avoid both problems: rounding 'up' to zero, and any underlying
problems above 2 GB.

-- 
Daniel Barker.

- Raw text -