Message-ID: <35C03674.CB7D7C9@gmx.net>
Date: Thu, 30 Jul 1998 09:01:40 +0000
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
MIME-Version: 1.0
To: DJ Delorie <dj AT delorie DOT com>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Very strange bug in re(f)malloc()
References: <199807281926 DOT PAA09160 AT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

DJ Delorie wrote :
> 
> Applied.  Gee, suddenly everyone's interested in the "other" malloc?

I didn't explicit tried the new (f)malloc. I siply came to this,
as I tested the alpha libc. Then I got everytime the segfaults
because of the bugs in malloc.c dealing with not testing the
given ptr in realloc for NULL (and I very often use the behaviour
of realloc(NULL, size) ). So I applied the posted patches to
malloc.c and fmalloc.c and then I replaced the object files in libc
via

ar r libc.a fmalloc.o malloc.o

without checking before, that the fmalloc.o wasn't yet in the libc.
So I had now the fmalloc.o before the malloc.o and came to the
new bug since now fmalloc.o is used instead of malloc.o.

Robert