From: Andrew Apted <ajapted AT netspace DOT net DOT au>
Date: Tue, 12 Sep 2000 14:27:58 +1000
To: djgpp AT delorie DOT com
Subject: Re: Malloc bug in DJGPP V2.03
Message-ID: <20000912142758.A583@ajax.netspace.net.au>
References: <20000911155441 DOT A493 AT ajax DOT netspace DOT net DOT au> <968648802 DOT 631222 AT shelley DOT paradise DOT net DOT nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <968648802.631222@shelley.paradise.net.nz>; from ejrh@paradise.net.nz on Mon, Sep 11, 2000 at 05:08:43PM +1200
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

Edmund Horner writes:

>  I'm afraid that I think you need to really worry about doing lots of
>  malloc'ing: it gets expensive if you use lots of small blocks.

Another data point (forgot this first time), the first thing I tried
was just allocating 9 MB worth of 32 byte structures.  That worked
fine.  Seems that mixing it with large reallocs is what causes DJGPP
to fail.

Cheers,
__
\/   Andrew Apted  <ajapted AT users DOT sourceforge DOT net>