This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/25793] dwarf2 debug info lacks linkage names for constructors & destructors
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Jan 2006 16:19:15 -0000
- Subject: [Bug debug/25793] dwarf2 debug info lacks linkage names for constructors & destructors
- References: <bug-25793-3402@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-15 16:19 -------
HUH???? The linkage_name is not needed for gdb, well it should not be needed.
This is also a dup of bug 11774 which has a better description of why
linkage_name is going away.
Also I tried with a newer gdb (6.3.50.20051027) and it worked with this
testcase and also with a class like:
class TestClass {
int y;
public:
int funcA(void);
TestClass(int x);
~TestClass(void);
TestClass();
};
And I could set the breakpoint:
(gdb) b TestClass::TestClass(int)
Breakpoint 1 at 0x804835b: file t.cc, line 20.
(gdb) b TestClass::TestClass()
Breakpoint 2 at 0x80483bd: file t.cc, line 10.
*** This bug has been marked as a duplicate of 11774 ***
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25793