Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch: implement new dynamic varobj spec
Date: Fri, 11 Sep 2009 23:55:00 -0000	[thread overview]
Message-ID: <19114.58228.563201.654364@totara.tehura.co.nz> (raw)
In-Reply-To: <m363bpgti0.fsf@fleche.redhat.com>

 > Nick> 1) Children are reported (and presumably created) in var-update
 > Nick> even though only a root variable object may have been created,
 > Nick> i.e., not -var-list-children has been invoked.
 > 
 > It should only report children if you previously requested them.

You're probably right, I can't reproduce this now.  I've been testing on
archer-tromey-python branch at git://sourceware.org/git/archer.git as I've
presumed that's where the patch posted here came from.

Incidentally git is a great improvement: I noticed that variable objects are
now staying in scope when the executable restarted and couldn't see why.  I
used 'git bisect' starting with 2000 revisions to find that it was due to Jan
Kratochvil's patch disabling randomisation.  I don't think I could have done
that with gdb in CVS.  I don't know how up to date the git mirror stays but it
would be grat if we could move to it at some point.  There appear to be lots
of other benefits.

 >...
 > Nick> Existing documentation uses @var for field names, while new uses @samp.
 > 
 > Yeah.  @var seems clearly wrong there.
 > I will change the new code though.

Really?  I thought @samp was wrong.  Eli will know.

I would really like to use these improvements in Emacs but the release isn't
far away.  So I would request that -enable-pretty-printing is marked as an
EXPERIMENTAL feature in the manual.  That way changes can be made without
anyone complaining.  Maybe by 7.1 early next year there will be frontends
that have worked out how to use it and that marking could be removed.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2009-09-11 23:55 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
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 [this message]
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=19114.58228.563201.654364@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