X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112091555.AA17701@clio.rice.edu>
Subject: Re: v2.03 refresh ready for review/testing
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Sun, 9 Dec 2001 09:55:57 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <003001c1809d$e0ff19c0$0102a8c0@acceleron> from "Andrew Cottrell" at Dec 09, 2001 09:39:01 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-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

> More testing info below. Have you been able to build GCC 2.9.5.3 on 2K or
> XP? I can build it on 98 using the GCC built..

No, out of time. (Working on use cases this weekend.  Must finish before
holidays so my slaves can work on details while I actually leave work.)

> I added the __maybe_fix_w2k_ntvdm_bug() call in  dosexec.c and re-built LIBC
> on Win 98 and then make, bash, binutils and GCC 2.9.5.3.  I then copied the
> updtaed exe files and unzipped the GCC zip files on my XP PC. The GCC build
> still failed in the same way as before.

I didn't think this should make any difference.  I installed SP2 on my W2K
home box last weekend and so my NTVDM nesting patch went away, so I'm 
seeing what breaks.  And since I'm not new binary clean I still see crashes.
I wish I had more time to help, but not for another week or so.

> I after a failure with not enough memory I run build again in the same cmd
> prompt it fails again, but then I don't have enough memory to load list. The
> following is the command prompt output from  the seond build:-

what does go32-v2 show for memory free?  Nothing we've touched (or not touched)
should make any difference on malloc ... if you were seeing ntvdm crashes
maybe dpmi memory blocks weren't being freed.  When in doubt, use the 
kill executable (it's on clio) and do kill ntvdm to get a clean working
environment.