Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: Obtaining number of children of a dynamic varobj
Date: Thu, 11 Feb 2010 17:23:00 -0000	[thread overview]
Message-ID: <hl1ed4$8fd$1@ger.gmane.org> (raw)
In-Reply-To: <58596C4646708B4BB990C4483997333001B639E9@usplmvpbe001.ent.rt.verigy.net>

Elmenthaler, Jens wrote:

> Hi,
> 
> Trying to enable the python pretty printers in the Eclipse CDT, a question about the MI API for
> varobjs arose.
> 
> If I read the documentation correctly, I should not call -var-list-children without the range of
> children, because in general I should assume that the varobj has a huge number of children and
> fetching them all is potential too expensive.
> 
> Quite reasonable sofar. Nevertheless, I have the problem that I have to know the number of
> children a dynamic varobj has.
> 
> The only way I see to obtain the number of children, however, is to call -var-list-children
> without a range specification. I can omit the values to be transferred. Does that have the same
> scalability issues, after all it still creates a varobj for each child?

[Please do not ask new questions by replying to an unrelated email]

Yes, it has the same issues. If you ask GDB about the number of children of a variable, and the
variable is uninitialized, GDB might not ever return. 

- Volodya



  reply	other threads:[~2010-02-11 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 17:38 GDB steping into STL Headers mweglicki8208
2010-02-11  2:26 ` Hui Zhu
2010-02-11  6:22 ` mweglicki8208
2010-02-11  9:28   ` Obtaining number of children of a dynamic varobj Elmenthaler, Jens
2010-02-11 17:23     ` Vladimir Prus [this message]
2010-02-11 17:56   ` GDB steping into STL Headers Tom Tromey
2010-02-11 19:03     ` Jim Ingham
2010-02-11 19:09       ` Daniel Jacobowitz
2010-02-11 19:12         ` Jim Ingham
2010-02-12  9:32           ` mweglicki8208
2010-02-12 10:43             ` Christophe-Marie Duquesne

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='hl1ed4$8fd$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb@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