Re: debugging for egcs

[Jeffrey A Law <law@cygnus.com>]

  In message < 199802230525.AAA03604@aura.saic1.com >you write:
  >   For Linux and Solaris the "pitiful" description sums up nicely.
  > 
  >   I *think* most of the egcs developers are aware that debugging 
  > C++ programs practically is impossible with gdb 4.16 at least on 
  > Solaris and Linux.
Use -gstabs to force stabs debugging until gdb-4.17 is released (it's
in beta testing right now).

  > (purify 4.1 and egcs 1.0.1 on SunOS 5.5)
  >   On Solaris purify and egcs don't seem to get along very well, the
  > only person around here who has got working binaries out of the 
This is pretty typical -- anytime purify sees something it does not
understand it craps out.  Having dealt with the problems with purify
and gcc over the years -- I can say that every case I've run into so
far where purify chokes has been a Purify bug.  ANd there's not much
we can do about them.

Checker and egcs-1.0 probably don't work.  That's because *many*
fixes went into checker after egcs-1.0 was released.

Current egcs snapshots should work as well as gcc-2.8 with checker;
any regressions would be considered a bug.  We'd need some testcases
to fix them -- but also note that everyone is quite busy, so it may
take a while before anyone can fix your problem.


jeff