Re: debug/8095: missing dwarf info for parent class

[Daniel Jacobowitz <drow@mvista.com>]

The following reply was made to PR debug/8095; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Cc: gcc-bugs@gcc.gnu.org, tom.horsley@ccur.com, gcc-gnats@gcc.gnu.org
Subject: Re: debug/8095: missing dwarf info for parent class
Date: Fri, 14 Mar 2003 16:51:45 -0500

 On Fri, Mar 14, 2003 at 03:48:12PM -0600, Wolfgang Bangerth wrote:
 > 
 > > As I mentioned, I'd like more opinions...
 > 
 > Sorry, I understood this but just wanted to raise the issue again -- 
 > opinions will not come in if the question bitrots in gnats :-) (Which is 
 > not your fault -- you had asked, but received no answers.)
 > 
 > > what if the class is emitted
 > > in a shared library not compiled using debug info, etc.?  I guess the
 > > question is: we want to emit debug information for all used types. 
 > > Does inheriting from a type count as using it?  If so we should
 > > probably be emitting debug info for Multiple1 in the example in this
 > > PR.
 > 
 > This doesn't strike me as a particularly useful idea, since then you would 
 > have to emit debug info in every compilation unit that includes a certain 
 > header file. This might be a lot of duplication.
 > 
 > If there are ways to tie debug output to a certain member of a class (just
 > as we do for vtables), then I would say this is a good idea. If someone
 > doesn't like this, then compile your library with -g.
 > 
 > But that's just my opinion.
 
 I guess that sounds pretty reasonable to me, too.
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer