From: Benjamin Kosnik <bkoz@redhat.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Jim Blandy <jimb@cygnus.com>, gdb@sources.redhat.com
Subject: Re: can't find class named `foo', as given by C++ RTTI
Date: Fri, 29 Jun 2001 11:34:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010629112925.25752A-100000@taarna.cygnus.com> (raw)
In-Reply-To: <87pubni1w7.fsf@cgsoftware.com>
> > In this case, GDB wasn't able to find the name std::numpunct.
Right.
> > Probably GDB should have been able to find std::numpunct.
Definitely, GDB should be able to find std::numpunct.
> > But does
> > the rest of the process look reasonable? That is, was the run-time
> > type of *__fp indeed `std::numpunct'? The output from `ptype'
> > suggests that its compile-time type is `class facet'. Perhaps
> > something went wrong well before we ever tried to look up the type
> > name.
>
> Nope. The name of the type in the symbol table is numpunct<char>,
> because of scoping problems.
Right. The ptype output is the base class, not what I really want to see.
I'd like to be able to look at the contents of the object, for instance.
I think this is a reasonable request.
You might want to look at this:
http://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-doxygen-3.0/class_std__numpunct.html
There's been some discussion on this thread: I'll give you a bit of time
to catch up.
-benjamin
next prev parent reply other threads:[~2001-06-29 11:34 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
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 [this message]
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.1010629112925.25752A-100000@taarna.cygnus.com \
--to=bkoz@redhat.com \
--cc=dan@cgsoftware.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.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