Mail Archives: djgpp/2001/07/03/08:30:03
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in
news:Pine DOT SUN DOT 3 DOT 91 DOT 1010703150621 DOT 19306K-100000 AT is:
> 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?
It was in a DOS box using Win 98 SP1. 96 MB physical memory installed and
go32-v2 reports:
DPMI memory available: 43136 Kb
DPMI swap space available: 51816 Kb
This sounds pathetic but I am not sure what version of GNU malloc I used. I
went to ftp.gnu.org and downloaded malloc.tar.gz. The change log included
indicates Thu Jul 11 18:15:04 1991 as the most recent change, and points to
the change log included in the C library for the more recent changes, but I
don't have it.
> 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.)
Definitely possible. Sorry I cannot provide more info at this point.
--
--------------------------------
A. Sinan Unur
http://www.unur.com/
- Raw text -