ddd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ddd/gdb


From: Tom Wurgler
Subject: Re: ddd/gdb
Date: Tue, 27 Jan 2004 12:50:09 -0500 (EST)

Recently Tim Mooney <address@hidden> wrote:

Tim> Date: Tue, 27 Jan 2004 10:45:20 -0600 (CST)
Tim> From: Tim Mooney <address@hidden>
Tim> Sender: address@hidden

Tim> In regard to: Re: ddd/gdb, Tom Wurgler said (at 9:32am on Jan 27, 2004):

Tim> >Using: DDD 3.3.8, gdb 6.0, gcc-3.3.2, HP-UX 11.0
Tim> >
Tim> >Ok, I've found some answers.  If I compile my fortran program with g77, 
then
Tim> >I can examine variables etc as I'd expect both in gdb command line and 
via ddd.
Tim> >If I use HP's f77, then I can't.
Tim> >
Tim> >This brings up some questions:
Tim> >
Tim> >1) DDD/GDB were compiled with gcc 3.3.2.  Does this mean I can only debug
Tim> >   programs compiled with the maching g77?

Tim> No, it just means that gdb 6.0 doesn't have good support for whatever
Tim> debugging format HP-UX's f77 uses.

Tim> >2) If I recompile DDD/GDB with HP's cc, can I debug f77 compiled programs
Tim> >   and g77 compiled programs?

Tim> No, that's not going to make any difference.

Yep, proved this already...

Tim> >3) Or am I just not getting it?  What am I missing?

Tim> gdb isn't handling the debugging symbols that HP's f77 is inserting.  It
Tim> doesn't matter what compiler you compile gdb with, it probably just
Tim> doesn't have some of the code it needs to support f77.  gdb's support
Tim> for every platform and every compiler is not perfect.  I think it's a
Tim> fantastic debugger, but it works very poorly on alpha-dec-osf, so when I
Tim> want to debug something on my workstation, I have to resort to another
Tim> debugger.

Ok.  I had already sent a note to the gdb help people.  If anything comes out
of that I'll let this list know.

Tim> You are sure, however, that f77 is compiling in debugging information,
Tim> right?

Yes, I did use the "-g".

Tim> You do know about HP's Wildebeast (wdb), right?  It's basically gdb 5.x
Tim> plus a huge number of improvements for HP-UX.  I believe it's still
Tim> command-equivalent to gdb, so you might be able to use it as a drop in
Tim> replacement for gdb in most circumstances.

I had seen this but figured I'd use the latest gdb.  I'll try it directly.

Thanks for the help.

tom




reply via email to

[Prev in Thread] Current Thread [Next in Thread]