Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Wed, 27 Jun 2001 22:51:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1010627224708.22381C-100000@taarna.cygnus.com> (raw)
In-Reply-To: <87hex1i3av.fsf@cgsoftware.com>

> > (gdb) p *__fp
> > can't find class named `std::numpunct<char>', as given by C++ RTTI
> This is no surprise.
> Without namespace support in the symbol table, sometimes the names
> aren't quite correct. 
> 5 to 1 says ptype 'numpunct<char>' works.

Yeah but doesn't really help me in terms of a debugging strategy.

:(

What about the demangling bits in the ptype output? Are those expected too?

Is special namespace support really necessary? I mean, the namespace 
qualified symbol *is* the correct name. Omitting the namespace is a bug.

> It's good to not have to worry about this stuff anymore. 
> I think i'll go implement dwarf2.1 namespace support in gcc.
> That way, I can at least say "Well, we output the info, but gdb can't
> use it".

Kind of depressing, but oh well. Any other takers?

-benjamin


  reply	other threads:[~2001-06-27 22:51 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 [this message]
2001-06-27 23:26     ` Daniel Berlin
2001-06-28  1:37       ` Benjamin Kosnik
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.1010627224708.22381C-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