From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>, david.carlton@sun.com
Cc: gdb@sources.redhat.com
Subject: Constructor names in the symbol table
Date: Fri, 17 Sep 2004 20:05:00 -0000 [thread overview]
Message-ID: <vt2u0twoe6x.fsf@zenia.home> (raw)
Hey you C++ guys (and anyone else who's interested):
I've noticed that constructors get entered into the full symbol table
under their unprefixed name. That is, the following code:
struct S
{
int x;
S(int);
};
S::S (int _x)
{
x = _x * 2;
}
int
main ()
{
S s(3);
}
as compiled by GCC 3.4 produces a LOC_TYPEDEF entry for S, and then
two LOC_BLOCK symbols for the in-charge and not-in-charge
constructors, whose names are S.
When I do something like set a breakpoint on S::S(int), I don't get a
match from the full symbol table; instead, I get a match on the
demangled names in the minimal symbol table.
Is this the way it's supposed to work? I would have expected
something in dwarf2read to have consulted processing_current_prefix
and produced a qualified name for the full symbol.
next reply other threads:[~2004-09-17 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 20:05 Jim Blandy [this message]
2004-09-17 22:55 ` Daniel Jacobowitz
2004-09-18 0:12 ` David Carlton
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=vt2u0twoe6x.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=david.carlton@sun.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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