From: nickrob@snap.net.nz (Nick Roberts)
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Patch: implement new dynamic varobj spec
Date: Fri, 11 Sep 2009 05:41:00 -0000 [thread overview]
Message-ID: <19113.58116.381538.294631@totara.tehura.co.nz> (raw)
In-Reply-To: <m3r5uejz4y.fsf@fleche.redhat.com>
Tom Tromey writes:
> This is the long-awaited dynamic varobj patch.
> It implements the spec as described by Vladimir:
>
> http://sourceware.org/ml/gdb/2009-07/msg00088.html
It's a big patch. Dynamic variable objects seem to behave differently
to the current ones:
1) Children are reported (and presumably created) in var-update even though
only a root variable object may have been created, i.e., not
-var-list-children has been invoked.
2) -var-update seems to list changes to children of dynamic objects in reverse
numerical order.
Does -var-set-update-range only work for dynamic variable objects - the
documentation doesn't say but I couldn't get it to work with current ones.
With dynamic variable objects I could restrict the range but it didn't seem
to match up (from seem to be ignored).
The new FROM TO arguments for -var-list-children work with current variable
objects but it seems that GDB just restricts what it prints but stores the
whole vector which doesn't seem to save memory. Would it not be better to
create children in the range specified since the array might be large and the
front end only needs the values it displays.
Likewise with -var-set-update-range: does GDB track all changes and just
report a restricted set, or restrict what it tracks?
I have a few thoughts about the documentation:
The field `in_scope' is already described with three possible values. It's
described again with just two.
The field `displayhint' seems very useful with -var-create but does it serve
any purpose when output with -var-update?
The field `has_more' seems to be overloaded depending on whether its output
from -var-create, -var-list-children or -var-update.
Existing documentation uses @var for field names, while new uses @samp.
I find varobj.c hard to read and some of what I say might be wrong but
hopefully there's more signal than noise.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-09-11 5:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 20:58 Tom Tromey
2009-09-11 5:41 ` Nick Roberts [this message]
2009-09-11 19:41 ` Tom Tromey
2009-09-11 20:49 ` Eli Zaretskii
2009-09-11 21:12 ` Tom Tromey
2009-09-12 8:08 ` Eli Zaretskii
2009-09-11 23:55 ` Nick Roberts
2009-09-14 19:59 ` Tom Tromey
2009-09-14 22:55 ` Nick Roberts
2009-09-15 15:37 ` Tom Tromey
2009-09-15 22:28 ` Nick Roberts
2009-09-16 5:45 ` Vladimir Prus
2009-09-16 9:56 ` Nick Roberts
2009-09-16 17:12 ` Tom Tromey
2009-09-16 22:26 ` Nick Roberts
2009-09-15 22:43 ` Nick Roberts
2009-09-16 5:39 ` Vladimir Prus
2009-09-16 9:36 ` Nick Roberts
2009-09-16 5:44 ` Vladimir Prus
2009-09-16 23:52 ` RFA: mark -enable-pretty-printing as experimental (Was: Patch: implement new dynamic varobj spec) Tom Tromey
[not found] ` <h8vk80$fqc$2@ger.gmane.org>
2009-09-18 10:02 ` Eli Zaretskii
2009-09-18 18:01 ` RFA: mark -enable-pretty-printing as experimental Tom Tromey
2009-09-14 19:56 ` Patch: implement new dynamic varobj spec Tom Tromey
2009-09-12 9:18 ` Eli Zaretskii
2009-09-14 20:03 ` Tom Tromey
2009-09-14 20:22 ` Eli Zaretskii
2009-09-14 21:29 ` Tom Tromey
2009-09-15 3:06 ` Eli Zaretskii
2009-09-14 11:24 ` Vladimir Prus
2009-09-16 23:53 ` Tom Tromey
2009-09-16 5:46 ` Vladimir Prus
2009-09-19 12:01 ` Matt Rice
2009-09-19 15:59 ` Joel Brobecker
2009-09-14 20:05 ` Tom Tromey
2009-09-14 20:24 ` Eli Zaretskii
2009-09-14 23:58 ` Nick Roberts
2009-09-18 9:29 ` Vladimir Prus
2009-09-18 18:25 ` Tom Tromey
2009-09-19 12:57 ` Vladimir Prus
2009-09-13 2:41 Nick Roberts
2009-09-14 20:12 ` Tom Tromey
2009-09-14 20:21 ` Tom Tromey
2009-09-15 0:03 ` Nick Roberts
2009-09-14 23:48 ` Nick Roberts
2009-09-15 15:38 ` Tom Tromey
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=19113.58116.381538.294631@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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