🚀 go-pugleaf

huttar@hp750.itg.ti.com (Lars Huttar) writes:

> Hamish.Macdonald@bnr.ca (Hamish Macdonald) writes:

> > 1) Get gcc to understand and insert HPUX debugging information into
> >    the object files it creates.  Also get gdb to understand and 
> >    retrieve HPUX debugging information from the executable.  To my
> >    knowledge, no-one has done this for a the 680x0 HP machines.  The
> >    folks at UUtah may have done this for the PA HP machines.

> Yes, you can get a modified gcc-2.3.3.u3 for PA HP's from
> jaugar.utah.edu:/dist.
> I just downloaded hpuxbin.tar.Z, which contained the executables
> for gcc, gdb, etc. that worked (with symbolic debugging & all)
> without modification.

I thought that HP was refusing to "free" its debugger symbol table
format (specifically the header file that defines all of the debugger
symbol data structures).  That would mean no Gnu product can read or
write HP debug info, because the FSF won't use code that isn't free,
and because HP won't let their debug info format be given away under
the FSF Copyleft.  This seems contrary to what Lars writes above.

Which is it: Do gcc and gdb understand HP debug info or don't they?

I too have heard about work at the University of Utah to teach gcc/gdb
about HP debug info, but I have also heard that HP has effectively
killed that work by refusing to free the necessary header file.
--
franl@centerline.com         "So what we've decided to do is set you up in
uunet!centerline!franl        Cicely, situated in an area that we Alaskans
617-498-3255 (USA)            refer to as The Alaskan Riviera."
PGP 2.0 public key available.