From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: Robustifying pretty-printers
Date: Thu, 09 Jul 2009 19:14:00 -0000 [thread overview]
Message-ID: <m3tz1llled.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200907092119.55363.vladimir@codesourcery.com> (Vladimir Prus's message of "Thu\, 9 Jul 2009 21\:19\:55 +0400")
>>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
Vladimir> There's also a question how frontend will know that there
Vladimir> are more children -- so that it can show "..." in the tree
Vladimir> view, or something. The best approach would be for GDB to
Vladimir> fetch one children more, and then use emit 'has-more' field
Vladimir> in -var-list-children output. The other alternative is for
Vladimir> frontend to fetch one more item than it wishes to display --
Vladimir> but such a logic has to be repeated for each
Vladimir> frontend. Anyway, this aspect seems independent from others,
Vladimir> so I can do it myself after you are done with the code
Vladimir> changes.
I don't mind doing it.
I was thinking of a 'dynamic' attribute, to let the FE know that the
numchild attribute cannot be believed. But, I think I like your
approach better.
Vladimir> We probably need a way to explicitly reset the
Vladimir> 'remembemered' limit on elements, so that frontend is not
Vladimir> forced to display 20 elements forever.
I couldn't find a reason why you wanted the range on
-var-list-children and not as a separate command. Could you explain
why? The reason I ask is that this issue was already solved in the
old patch: you could use -var-set-child-range to set and also unset
the range.
Tom
next prev parent reply other threads:[~2009-07-09 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 10:11 Vladimir Prus
2009-06-13 10:21 ` Vladimir Prus
2009-06-15 12:28 ` Phil Muldoon
2009-06-15 12:39 ` Vladimir Prus
2009-06-15 12:55 ` Daniel Jacobowitz
2009-06-15 13:25 ` Vladimir Prus
2009-06-16 7:22 ` André Pönitz
2009-06-15 20:01 ` Tom Tromey
2009-06-16 8:22 ` Vladimir Prus
2009-07-07 21:48 ` Tom Tromey
2009-07-09 17:20 ` Vladimir Prus
2009-07-09 19:14 ` Tom Tromey [this message]
2009-07-10 6:13 ` Vladimir Prus
2009-07-10 16:25 ` Tom Tromey
2009-07-10 16:40 ` Vladimir Prus
2009-07-10 16:48 ` Tom Tromey
2009-07-10 18:46 ` Vladimir Prus
2009-07-10 18:52 ` 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=m3tz1llled.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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