From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10102261811.AA12134@clio.rice.edu>
Subject: Re: Eradicating djgpp W2000 problem
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Mon, 26 Feb 2001 12:11:20 -0600 (CST)
Cc: michael DOT allison2 AT sympatico DOT ca (Michael Allison), djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.1010226173136.24373F-100000@is> from "Eli Zaretskii" at Feb 26, 2001 05:32:16 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> > The crashes occur "randomly" - by that I mean if you run the exact same
> > sequence 10 times it may work 9 times out of 10.
> > 
> > I also observed once (I believe... hard to be sure when you only see it once)
> > a crash in GCC alone - only a single nesting.
> 
> Thanks.  Could you please tell what programs did you invoke?  Was that 
> GCC from Make, or something else?

GCC from the command line (CMD.exe) crashed the VDM once if I remember
correctly.  Usually I was seeing lots of crashes running make, which then
calls GCC.  We tried patching make to not hook interrupts, or to toggle
exceptions - none of which seemed to help.

I did some playing with trying to "go32 gcc" and "go32 make" to add
additional nesting levels and got interesting results I don't remember
and couldn't explain.