public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dberlin@sources.redhat.com
To: dberlin@sources.redhat.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, thor@math.TU-Berlin.DE
Subject: Re: c++/8256: g++ -ggdb does not emmit debug info for subclasses
Date: Thu, 17 Oct 2002 10:35:00 -0000	[thread overview]
Message-ID: <20021017173518.27309.qmail@sources.redhat.com> (raw)

Synopsis: g++ -ggdb does not emmit debug info for subclasses

Responsible-Changed-From-To: unassigned->dberlin
Responsible-Changed-By: dberlin
Responsible-Changed-When: Thu Oct 17 10:35:17 2002
Responsible-Changed-Why:
    Me
State-Changed-From-To: open->closed
State-Changed-By: dberlin
State-Changed-When: Thu Oct 17 10:35:17 2002
State-Changed-Why:
    This is a gdb problem.
    Not a g++ one.
    It's doing the lookup wrong.
    
    In fact, it tells you so.
    "the class A does not have any method named B"
    It's trying to find a method named B, in class A, instead of looking for a method named Hello, in class "A::B".
     
    You can prove it to yourself by using 
    rb A::C::Hello
    
    Which will avoid the normal lookup strategy (It will set breakpoints based on a regexp, thus, it just searches all the symbols, rather than trying to find just one symbol through the normal lookup path).
    
    I also looked at the generated debug info, just to make sure, and we are outputting the proper debug info.

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


                 reply	other threads:[~2002-10-17 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021017173518.27309.qmail@sources.redhat.com \
    --to=dberlin@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=thor@math.TU-Berlin.DE \
    /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).