Mail Archives: djgpp/2000/01/18/17:08:27
"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
- Raw text -