This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFA: fix PR python/11792
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 02 Sep 2010 20:05:54 +0300
- Subject: Re: RFA: fix PR python/11792
- References: <m3zkwdozop.fsf@fleche.redhat.com> <m3y6boj7y8.fsf@fleche.redhat.com> <83sk1wj6tq.fsf@gnu.org> <m3pqwzj1cf.fsf@fleche.redhat.com> <83pqwzkeyi.fsf@gnu.org> <m3wrr58501.fsf@fleche.redhat.com> <83zkw0j15r.fsf@gnu.org> <m31v9c88di.fsf@fleche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 02 Sep 2010 09:36:57 -0600
>
> Eli> Now I'm confused: earlier you told that the current language doesn't
> Eli> matter, but now you say that only information emitted by the C++
> Eli> compiler will do, which seems a contradiction. What am I missing?
>
> The current language is a gdb setting. It is independent of objects in
> the inferior.
That's a misunderstanding, then: I didn't mean (and didn't say)
"current language".
So I understand now that this feature will work only while debugging a
C++ program that includes RTTI for the object in question. Otherwise,
it will just return the type of the value as in "ptype foo", is that
right? If so, maybe just mention this fact, since someone who debugs
a non-C++ program will not necessarily understand what is meant by
"the static type".
Thanks.