public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: drow@sources.redhat.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tom.horsley@ccur.com
Subject: Re: debug/8095: missing dwarf info for parent class
Date: Fri, 14 Mar 2003 21:19:00 -0000	[thread overview]
Message-ID: <20030314211918.19230.qmail@sources.redhat.com> (raw)

Synopsis: missing dwarf info for parent class

Responsible-Changed-From-To: unassigned->drow
Responsible-Changed-By: bangerth
Responsible-Changed-When: Fri Mar 14 21:19:17 2003
Responsible-Changed-Why:
    Analyzed this PR
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Fri Mar 14 21:19:17 2003
State-Changed-Why:
    Daniel, what's the state of this? If debug generation is
    really tied to the definition of the first virtual non-
    abstract function, then I can't see how this could be
    wrong: no program can be linked without having such a 
    definition, so at one point or other, a definition has to
    be given, and then the executable also contains the debug
    information. Unfortunately, my versions of readelf seems
    to be too old to verify this myself.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8095


             reply	other threads:[~2003-03-14 21:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 21:19 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 22:06 Wolfgang Bangerth
2003-03-14 21:56 Wolfgang Bangerth
2003-03-14 21:56 Daniel Jacobowitz
2003-03-14 21:36 Daniel Jacobowitz
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=20030314211918.19230.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=drow@sources.redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=tom.horsley@ccur.com \
    /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).