Date: Tue, 18 Jan 2000 12:30:17 -0600
From: Weiqi Gao <weiqi DOT gao AT edwardjones DOT com>
Subject: Re: GCC bugs
To: djgpp AT delorie DOT com
Message-id: <3884B139.65F90FCF@edwardjones.com>
Organization: Edward Jones
MIME-version: 1.0
X-Mailer: Mozilla 4.51 [en]C-CCK-MCD   (WinNT; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
References: <01bf611a$9c6e9500$LocalHost AT alex> <3883BCC2 DOT 2CC1DCD9 AT a DOT crl DOT com>
 <01bf61c3$70f0a7c0$LocalHost AT alex>
Reply-To: djgpp AT delorie DOT com

"Alexei A. Frounze" wrote:
> 
> 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.

I tried both methods yesterday and I got the same .o files.  There was
no ".eh_fram" section in either of them.  Maybe someone who knows
".eh_fram" sections better can help you with the problem.

> > 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.

--
Weiqi Gao
weiqigao AT a DOT crl DOT com