Message-Id: <3.0.5.32.19981018132342.009095b0@ns1.avatar.com>
X-Sender: kory AT ns1 DOT avatar DOT com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Sun, 18 Oct 1998 13:23:42 -0600
To: djgpp AT delorie DOT com, orangy AT inetlab DOT com
From: Kory Hamzeh <kory AT avatar DOT com>
Subject: Re: gcc 2.7.2 crashing under win95
In-Reply-To: <362A38CA.DFE818FA@inetlab.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19981017134344 DOT 00b779c0 AT ns1 DOT avatar DOT com>
 <3 DOT 0 DOT 5 DOT 32 DOT 19981018094104 DOT 00b17360 AT ns1 DOT avatar DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com

At 12:51 AM 10/19/98 +0600, Ilya Ryzhenkov wrote:
>Kory Hamzeh wrote:
>> Anyway, the first blue screen now says: "exception 0E in VxD VREDIR ..
>> called from IFSMGR. Please any key to return." When I press a key, I then
>> get "exception 0E in VNBI .. called from VTDI". And it goes on and on until
>> the system basically locks up.
>It looks like you redirect output of the program or it is done somehow
>implicitly.
>Please post how do you start your program, which shell do you use,
>etc...
>

Hi Ilya,

I guess I thought I made that clear. I run a dos box under win95 using the
normal win96 shell (command.com??). I invoke gcc as follows:

	gcc -o x x.c

When I invoke gcc with the -v option, it is stubify that causes the crash.
Let me know if there is anymore info needed. I haven't figured out how to
redirect the output of "gcc -v" to a file so that I can e-mail that.

Kory