From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Add -var-info-path-expression command
Date: Tue, 04 Apr 2006 16:13:00 -0000 [thread overview]
Message-ID: <20060404161314.GA4016@nevyn.them.org> (raw)
In-Reply-To: <200604041744.37005.ghost@cs.msu.su>
On Tue, Apr 04, 2006 at 05:44:36PM +0400, Vladimir Prus wrote:
> On Tuesday 04 April 2006 17:26, Daniel Jacobowitz wrote:
> > On Tue, Apr 04, 2006 at 11:22:02AM +0400, Vladimir Prus wrote:
> > > Any comments on this yet? I believe we've discussed the rationale for
> > > -var-info-path-expression command in the main list, and agreed that it's
> > > necessary.
> >
> > Yes, I think we've agreed on that.
> >
> > It would be nice if there were test cases and documentation to go with
> > this.
>
> Is this a hard requirement?
To merge the patch? Yes, I think so.
It also has a lot of formatting issues, at least one APPLE LOCAL
marker, and bunch of untranslated error messages (which might be
inappropriate uses of error; some of them maybe should be internal
errors instead; I didn't check yet).
> > I've been putting off looking at this patch, because (A) I had a whole
> > lot of other patches to review, and (B) it's huge and gnarly. I am not
> > really sure that Apple took the right approach with C++ classes and
> > run-time type information. Maybe they did, but it's not at all
> > obvious.
>
> FWIW, I'm not 100% understand what they did, but this does not matter. My
> patch does some surgery to grab only -var-info-path-expression, and no
> type/RTTI related changes.
+ /* This is the most specific type of a C++ class object - as obtained from
+ value_rtti_type. It will be set in two cases:
+
+ a) If the varobj is a pointer or reference to a C++ object. In this
+ case the dynamic_type will be a pointer or reference to the full
+ class.
+ b) If the varobj is a C++ object. In this case, it will be the type
+ of the full object, and the value field will be adjusted by
+ value_full_object to the full object. */
+ struct type *dynamic_type;
+
And the related code below.
I'm not saying it's right or wrong, by the way. I'm saying it's
complicated and I need to spend a while thinking about it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-04 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 18:37 Vladimir Prus
2006-04-04 7:25 ` Vladimir Prus
2006-04-04 13:26 ` Daniel Jacobowitz
2006-04-04 13:45 ` Vladimir Prus
2006-04-04 16:13 ` Daniel Jacobowitz [this message]
2006-04-04 18:44 ` 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=20060404161314.GA4016@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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