Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH:MI] Return a subset of a variable object's children
Date: Wed, 30 Apr 2008 12:20:00 -0000	[thread overview]
Message-ID: <fv9djr$av8$1@ger.gmane.org> (raw)
In-Reply-To: <200804301100.21674.apoenitz@trolltech.com>

André Pönitz wrote:

> On Wednesday 30 April 2008 08:24:30 Vladimir Prus wrote:
>> Nick Roberts wrote:
>> > [...]
>> > I was thinking that only a small number of children would ever exist
>> > simultaneously.  Scrolling might make that a larger number but maybe
>> > it could be arranged to delete children that go out of view.
>> 
>> 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.

> and one-shot 'expression evaluation' and one-shot 'children listing'.

What is 'expression evaluation'. As for one-shot 'children listing' -- the
idea is that you can pass the number of children to create for -list-children,
and GDB won't do anything about children beyond this range.

> I would expect this to be much simpler to implement on the gdb side and
> gives all the flexibility needed (as far as I am concerned) on the
> frontend side.
> 
> Complex containers may do all kind of funny stuff behind the debugger's
> back (like reallocation, rebalancing, renumbering, moving stuff to and from
> secondary memory) which a frontend might want to handle transparently.
> I would not expect gdb to even be aware of that (let alone to handle(!) it).
> 
> Also, hard-wiring behaviour to certain types calls for trouble on the
> frontend side. E.g. if there's a std::string member somewhere I might want
> to see it as something "human readable" (-> 1 child), or a byte array
> (->lots of children), or maybe a structured view if it is XML (-> some children).
> So whatever behaviour is hard-wired will be wrong for  n - 1 use cases.

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)
2. Just get the raw data and show it as you see fit.

- Volodya


> 
> Regards,
> Andre'



  reply	other threads:[~2008-04-30  9:20 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 [this message]
2008-04-30 12:53           ` André Pönitz
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='fv9djr$av8$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.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