From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10108241909.AA14954@clio.rice.edu>
Subject:	Re: gcc-3.0.1 WinXP and lfn=n
To:	djgpp-workers AT delorie DOT com
Date:	Fri, 24 Aug 2001 14:09:32 -0500 (CDT)
In-Reply-To:	<10108241804.AA16934@clio.rice.edu> from "Charles Sandmann" at Aug 24, 2001 01:04:13 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> 
> Using xgcc (non-stripped).
> 
> It's an evil one.  Kills NTVDM completely, quietly, back to command line
> with no indication of what's happened.  If I do one step too many I'm
> back at the command line.

It dies someplace in stat() - we enter and NTVDM goes away.
The name we send it when it does does not exist, but seems OK to me:
("d:/djgpp/bin/djgpp/3.01/as.exe")
However this is the CD drive and the device is not ready.

The previous calls to stat() had some really bad things sent:
"c:/djgpp/lib/gcc-lib/djgpp/3.01/../../../../djgpp/bin/djgpp/3.01/as.exe"

I don't think we are supposed to send DOS strings that long.  I'm not
sure which of these two caused the problem (or if a combo).

I'm not sure what algorithm GCC uses trying to find as, but it looks like
it's checked every random combo at this point and still hasn't found it :-)

- Raw text -