From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR python/11792
Date: Tue, 07 Sep 2010 21:01:00 -0000 [thread overview]
Message-ID: <m3zkvtwfq2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83y6bkhy8d.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 02 Sep 2010 20:05:54 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> The current language is a gdb setting. It is independent of objects in
>> the inferior.
Eli> That's a misunderstanding, then: I didn't mean (and didn't say)
Eli> "current language".
Ok.
Eli> So I understand now that this feature will work only while debugging a
Eli> C++ program that includes RTTI for the object in question. Otherwise,
Eli> it will just return the type of the value as in "ptype foo", is that
Eli> right?
That is reasonably accurate.
Eli> If so, maybe just mention this fact, since someone who debugs
Eli> a non-C++ program will not necessarily understand what is meant by
Eli> "the static type".
I still think the text is reasonably clear, but if you want to change
it, that is fine by me.
Tom
next prev parent reply other threads:[~2010-09-07 18:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 20:13 Tom Tromey
2010-08-30 18:01 ` Tom Tromey
2010-08-30 18:24 ` Eli Zaretskii
2010-08-30 20:24 ` Tom Tromey
2010-08-30 20:43 ` Eli Zaretskii
2010-09-01 23:01 ` Tom Tromey
2010-09-02 10:32 ` Eli Zaretskii
2010-09-02 15:48 ` Tom Tromey
2010-09-02 18:40 ` Eli Zaretskii
2010-09-07 21:01 ` Tom Tromey [this message]
2010-09-22 16:33 ` Eli Zaretskii
2010-09-22 18:47 ` Tom Tromey
2010-09-22 19:15 ` Eli Zaretskii
2010-09-22 19:17 ` Joel Brobecker
2010-09-22 19:19 ` Eli Zaretskii
2010-09-22 19:26 ` Tom Tromey
2010-09-22 19:59 ` Eli Zaretskii
2010-09-22 20:57 ` Tom Tromey
2010-09-23 12:42 ` Eli Zaretskii
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=m3zkvtwfq2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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