From: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT n-o-s-p-a-m DOT ru>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GCC bugs
Date: 18 Jan 2000 14:43:20 GMT
Organization: MTU-Intel ISP
Lines: 31
Message-ID: <01bf61c3$70f0a7c0$LocalHost@alex>
References: <01bf611a$9c6e9500$LocalHost AT alex> <3883BCC2 DOT 2CC1DCD9 AT a DOT crl DOT com>
NNTP-Posting-Host: dial56064.mtu-net.ru
X-Trace: gavrilo.mtu.ru 948206600 16093 195.34.56.64 (18 Jan 2000 14:43:20 GMT)
X-Complaints-To: usenet-abuse AT mtu DOT ru
NNTP-Posting-Date: 18 Jan 2000 14:43:20 GMT
X-Newsreader: Microsoft Internet News 4.70.1155
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi!

> It means your first method and second method didn't do the same thing. 
> Are you using aliases, doekey macros? Do you have duplicated commands in
> your $PATH?  Try the two methods with absolute paths in all places.
> 
> Do you have another brand of GCC installed?  An earlier version?

I have the only(!) copy of the GCC on the HDD. Furthermore, this bug cames
on both computers where I use DJGPP. And the bug is present in 2.81 and
2.95.2 versions of GCC.
I also don't have any other programs or batch files with the GCC name. Try
to compile something two different ways as I tried. Tell me of the result
then.

> The GCC documentation says clearly that a GCC crash under any
> circumstance, with legal or illegal source code, is considered a bug. 
> If you can reproduce the crash, report a bug with ways to reproduce the
> behavior.

So I think they will never fix the bug because it cames unpredictable. I
don't change anything, I just run the GCC once more and it works fine.


Bye.
Alexei A. Frounze
-- 
P.S. In order to reply via e-mail, remove the "n-o-s-p-a-m." substring out
of the e-mail address.