X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Wed, 16 Jan 2002 18:29:49 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: sandmann AT clio DOT rice DOT edu
Message-Id: <2110-Wed16Jan2002182948+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au
In-reply-to: <10201161432.AA16707@clio.rice.edu> (sandmann@clio.rice.edu)
Subject: Re: ls weirdness on root drive
References:  <10201161432 DOT AA16707 AT clio DOT rice DOT edu>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Wed, 16 Jan 2002 08:32:11 -0600 (CST)
> 
> > Here's an idea: link a small test program with malloc-debugging routines, 
> > and try to see if the debug output tells something useful.  In particular, 
> > dumping all the allocated buffers in several strategic places during the 
> > startup code might be helpful.  See the docs for `mallinfo', 
> > `malloc_debug', and `mallocmap' (in the CVS version of the library), for 
> > more info.
> 
> I can't get it to fail in a small test program.  I can't even get the 
> current binary to fail under the debugger.  (If it would, I can work
> with the disassembly and source to find/fix).
> 
> But the current binary reliably fails without the debugger, or fails 
> differently when run from go32-v2, or fails differently with a different
> djgpp.env size.

It might still be useful to try to link the failing program with YAMD
and run that on plain DOS with CWSDPMI.