From: Benjamin Kosnik <bkoz@redhat.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb@sources.redhat.com
Subject: Re: can't find class named `foo', as given by C++ RTTI
Date: Thu, 28 Jun 2001 01:37:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010628013305.22816B-100000@taarna.cygnus.com> (raw)
In-Reply-To: <873d8li0hh.fsf@cgsoftware.com>
> Does that occur with both dwarf2 and stabs?
Yes.
> > Is special namespace support really necessary?
> Special?
> You mean special as in "any whatsoever"?
> Yes.
Aaaaaaaaah.
> The dwarf2 standard doesn't say the names given are to be fully
> qualified. In fact, just the opposite is the general practice. If you
> want fully qualified names, you are expected to generate them, which
> isn't all that tricky to do.
Ok.
> Think of what happens if you have:
>
> DW_TAG_namespace:
> DW_AT_name "std"
> DW_TAG_class:
> DW_AT_name "std::numpunct<char>"
> ...
> DW_TAG_namespace:
> DW_AT_name "danspace"
> DW_TAG_using:
> DW_AT_name "std"
>
> Now, if we don't change the symbol structures, and do this by copying
> all the symbols in std to the block for danspace, gdb will print out, and
> treat, the names as if they were "danspace::std::numpunct<char>".
>
> This is why we need to generate the qualified names ourselves.
>
> The non-hack solution here is to add namespace support to gcc's dwarf2
> output, and gdb's dwarf2 reader.
Ok. Thanks. I wasn't thinking about types, and aliasing namespaces. It's
encouraging to see the support for scoping in other parts of gdb,
although symbol support seems lacking.
-benjamin
next prev parent reply other threads:[~2001-06-28 1:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 21:55 Benjamin Kosnik
2001-06-27 22:25 ` Daniel Berlin
2001-06-27 22:51 ` Benjamin Kosnik
2001-06-27 23:26 ` Daniel Berlin
2001-06-28 1:37 ` Benjamin Kosnik [this message]
2001-06-27 23:06 ` Daniel Berlin
2001-06-28 1:32 ` Benjamin Kosnik
2001-06-28 16:02 ` Daniel Berlin
2001-06-28 16:14 ` Benjamin Kosnik
2001-06-29 15:14 ` Jim Blandy
2001-06-29 23:43 ` Daniel Berlin
2001-06-30 10:14 ` Jim Blandy
2001-06-29 11:15 ` Jim Blandy
2001-06-29 11:20 ` Daniel Berlin
2001-06-29 11:34 ` Benjamin Kosnik
2001-06-29 11:38 ` Daniel Berlin
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=Pine.SOL.3.91.1010628013305.22816B-100000@taarna.cygnus.com \
--to=bkoz@redhat.com \
--cc=dan@cgsoftware.com \
--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