Mail Archives: djgpp/2008/07/08/23:26:37

X-Authentication-Warning: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <>
Date: Wed, 09 Jul 2008 06:26:11 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Thunderbird (X11/20080501)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: libstdc++ writev/2.04/patches upstream?
References: <200807070405 DOT m67451dZ010910 AT delorie DOT com> <BAY139-W19808358F507B7930E7F6EE6940 AT phx DOT gbl> <200807071920 DOT m67JKA4v032518 AT envy DOT delorie DOT com> <487290E2 DOT 86197C00 AT yahoo DOT com> <200807072300 DOT m67N0t0Y005696 AT envy DOT delorie DOT com> <4872DFDB DOT 3E4BE7C1 AT yahoo DOT com> <200807080501 DOT m6851VZ8015818 AT envy DOT delorie DOT com> <4873E90E DOT B2B957F9 AT yahoo DOT com>
In-Reply-To: <>
Reply-To: djgpp AT delorie DOT com

CBFalconer wrote:
> DJ Delorie wrote:  ** and snipped references to nmalloc **
>>>> Did you ever resolve all the issues we had with it?
>>> Never had any issues reported.
> Never saw them, and I just looked at that and at:
> <>
> (per Andris Pavenis)
> and I see nothing that I can attack, in fact nothing definite. 
> Bear in mind that I do not use XP.  I do know I can crash the
> original malloc system fairly easily.

The first message of the thread is

I included there the source of my initial test program used for profiling. Remove
shuffling addresses and freeing memory, link it with nmalloc and You will get
what I use for testing when large enough number of allocations were specified
(like more that 1000000, You should have plenty of memory for that). This
test program randomly crashed when linked with nmalloc and never for me
if with DJGPP v2.04 own malloc (for this test slowness of free() does not
matter of course).

I do not know whether it is possible to reproduce the problem on system different from


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019