DG/UX Dwarf1 Problem - Switch to GDB?

[Eric Raskin]

Just to make sure...

You understand that when I change from dwarf1 to dwarf2 debugging format, egcs will no longer work with the native debugging tools.
Isn't this an external constraint?  Of course, egcs doesn't work with the native debugging tools now, so I guess it's not a big
difference, huh? :-)

If it is decided that I should change the default, how do I document it so that future users know they need gdb as well?

Also, any hints on setting the debugging switch based on language, so that I can leave dwarf1 for gcc and set dwarf2 for g++?

  Eric

-----Original Message-----
From: Jeffrey A Law [ mailto:law@cygnus.com ]
Sent: Wednesday, June 30, 1999 9:34 AM
To: Robert Lipe
Cc: Eric Raskin; egcs@egcs.cygnus.com; takis@dpmms.cam.ac.uk
Subject: Re: DG/UX Dwarf1 Problem - Switch to GDB?


  In message < 19990630082041.C17422@rjlhome.sco.com >you write:
  > You're asking about the default debugging format emitted, right?
  >
  > If you go to stabs you're going to require the GNU assembler.  Dwarf2
  > seems to be coming into favor amongst the GDB and EGCS people that know
  > about such things but it can still be a little lonely.
Generally we want to see ports moving to dwarf2.  Stabs is a close second.
dwarf1 and others are not recommended as the default format, except where
imposed by external constraints.

  > You could but my experience is that it's painful.  Mixing debugging
  > formats in the same executable (and linking C and C++ is common) never
  > brought me much joy.
I've done this quite a bit in the past.  If it doesn't work, then I would
consider that a bug in gdb.  In my particular case I often end up with a
mix of stabs & HP's debug records in my executables.  gdb handles this just
fine.

eff