Date: Tue, 3 Jul 2001 15:08:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "A. Sinan Unur" <asu1 AT cornell DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: malloc() problem, DJDEV 203
In-Reply-To: <Xns90D2E5B62E697ASINANUNUR@132.236.56.8>
Message-ID: <Pine.SUN.3.91.1010703150621.19306K-100000@is>
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 3 Jul 2001, A. Sinan Unur wrote:

> Anyway, GNU Malloc seems to work as expected (returning null) for large 
> allocations up to 0xFFF5FFFF. After that it goes into an infinite loop (can 
> still do CTRL-BREAK to exit).

On what OS was that?  And what version of GNU malloc did you try?

I recently found a nasty bug in gmalloc, whereby large allocation 
requests were treated as negative numbers in some of the subroutines of 
gmalloc.  It's quite possible that the loop you see is due to that.
(The reason of the bug was that they mixed signed and unsigned, if 
someone's interested.)