This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/8256: g++ -ggdb does not emmit debug info for subclasses
- From: dberlin at sources dot redhat dot com
- To: dberlin at sources dot redhat dot com, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, thor at math dot TU-Berlin dot DE
- Date: 17 Oct 2002 17:35:18 -0000
- Subject: Re: c++/8256: g++ -ggdb does not emmit debug info for subclasses
- Reply-to: dberlin at sources dot redhat dot com, dberlin at sources dot redhat dot com, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, thor at math dot TU-Berlin dot DE, gcc-gnats at gcc dot gnu dot org
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