public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: drow@sources.redhat.com
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/8095: missing dwarf info for parent class
Date: Fri, 14 Mar 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030314220600.10570.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Daniel Jacobowitz <drow@mvista.com>
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 15:58:32 -0600 (CST)

 > > 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.
 > 
 > I guess that sounds pretty reasonable to me, too.
 
 So shall I close the report then? Note that I couldn't verify that the 
 debug info is actually emitted when the vtable is emitted -- could you 
 check this?
 
 Thanks
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-14 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 22:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 15:05 bangerth
2003-04-15 13:36 Daniel Jacobowitz
2003-03-17 14:26 Daniel Jacobowitz
2003-03-17 13:06 Horsley Tom
2003-03-14 21:56 Daniel Jacobowitz
2003-03-14 21:56 Wolfgang Bangerth
2003-03-14 21:36 Daniel Jacobowitz
2003-03-14 21:19 bangerth
2002-10-01 12:16 Daniel Jacobowitz
2002-10-01  5:06 Horsley Tom
2002-09-30 13:46 Daniel Jacobowitz
2002-09-30  5:46 tom.horsley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030314220600.10570.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=drow@sources.redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).