public inbox for
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <>
Subject: [Bug mi/14607] -var-list-children reports wrong numchild count
Date: Wed, 25 May 2022 19:00:41 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
'numchild' isn't reliable for a dynamic varobj.
This is documented in the MI docs:

     The number of children of the varobj.  This number is not
     necessarily reliable for a dynamic varobj.  Instead, you must
     examine the 'has_more' attribute.

This is a little confusing because in this command:

-var-list-children --all-values struct1.public
std::allocator<int> >",displayhint="array",dynamic="1"}],has_more="0"

... the has_more here refers to 'struct1.public' (which really only
does have one child), and 'a' doesn't have a has_more here.
Instead one must list the children of 'a' to find out.

So, I'm somewhat inclined to mark this as not a bug.

You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-05-25 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22  9:19 [Bug mi/14607] New: " niko.sams at gmail dot com
2012-09-22  9:21 ` [Bug mi/14607] " niko.sams at gmail dot com
2012-09-22  9:24 ` niko.sams at gmail dot com
2022-05-25 19:00 ` tromey at sourceware dot org [this message]
2023-08-31 17:29 ` tromey at sourceware dot org

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).