From: "André Pönitz" <apoenitz@trolltech.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH:MI] Return a subset of a variable object's children
Date: Wed, 30 Apr 2008 12:53:00 -0000 [thread overview]
Message-ID: <200804301140.26347.apoenitz@trolltech.com> (raw)
In-Reply-To: <fv9djr$av8$1@ger.gmane.org>
On Wednesday 30 April 2008 11:19:59 Vladimir Prus wrote:
> André Pönitz wrote:
> >> I wonder if deleting children that are not visible is possible/desirable.
> >
> > Well, I would still prefer a simple toggle that would allow me to switch off
> > any automatic creation of children
>
> There's no automatic creation. Until you do -list-children, no child is created.
That's what I meant. Right now I can't get a list of children without
varobjects being created.
> > and one-shot 'expression evaluation' and one-shot 'children listing'.
>
> What is 'expression evaluation'.
A shortcut for
-var-create foo * exp
-var-evaluate-expression foo
-var-delete foo
optionally including a
-var-list-children foo
Maybe its already there and I just did not see it...
> [...]
> I'm afraid I don't get your point. If you want funny representations of
> any type you can either:
>
> 1. Use Python visualizers (that can be switched on the fly)
Right. I guess that's probably the route to go for me in the long run.
I am a bit scared by the additional dependency, though, so I wouldn't
mind to have a reasonably well working 'pure MI' solution as fallback,
too.
> 2. Just get the raw data and show it as you see fit.
This does not work too well with structures containing pointers
or such. It's fine for 'position independent' data like bitmaps or
so, though.
Andre'
next prev parent reply other threads:[~2008-04-30 9:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:34 Nick Roberts
2008-04-29 15:58 ` Marc Khouzam
2008-04-30 7:02 ` Nick Roberts
2008-04-30 9:20 ` Vladimir Prus
2008-04-30 9:25 ` Nick Roberts
2008-04-30 9:39 ` Vladimir Prus
2008-04-30 16:29 ` Marc Khouzam
2008-05-01 15:56 ` Vladimir Prus
2008-05-01 17:29 ` Marc Khouzam
2008-05-01 12:15 ` Nick Roberts
2008-05-10 14:45 ` Nick Roberts
2008-05-28 19:15 ` Vladimir Prus
2008-05-29 12:01 ` Nick Roberts
2008-04-30 16:22 ` Marc Khouzam
2008-05-01 15:54 ` Vladimir Prus
2008-05-01 18:14 ` Marc Khouzam
2008-05-01 18:40 ` Vladimir Prus
2008-05-01 20:49 ` Daniel Jacobowitz
2008-05-01 23:38 ` Nick Roberts
2008-05-02 0:58 ` Marc Khouzam
2008-05-11 17:45 ` Vladimir Prus
2008-04-30 10:47 ` André Pönitz
2008-04-30 12:20 ` Vladimir Prus
2008-04-30 12:53 ` André Pönitz [this message]
2008-04-30 13:11 ` Vladimir Prus
2008-04-30 12:44 ` Nick Roberts
[not found] ` <200804301244.55116.apoenitz@trolltech.com>
2008-04-30 13:16 ` André Pönitz
2008-05-01 6:27 ` Nick Roberts
2008-05-05 11:46 ` André Pönitz
2008-04-30 14:59 ` Marc Khouzam
2008-05-01 12:06 ` Nick Roberts
2008-05-01 14:22 ` Marc Khouzam
2008-05-01 20:41 ` Daniel Jacobowitz
2008-04-30 8:59 ` Vladimir Prus
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=200804301140.26347.apoenitz@trolltech.com \
--to=apoenitz@trolltech.com \
--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