public inbox for
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <>
Subject: [Bug varobj/23367] MI emits error about "Duplicate variable object name" if pretty-printer prepends to children on subsequent enumerations
Date: Thu, 31 Aug 2023 17:17:22 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
          Component|mi                          |varobj
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I guess I don't understand why gdb doesn't just fully
synthesize all the names.  But maybe this goes along
with "pretty printing v2", since we may need to split
the name / access fields.

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

  parent reply	other threads:[~2023-08-31 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-05-25 18:49 ` [Bug mi/23367] " tromey at sourceware dot org
2023-08-31 17:17 ` tromey at sourceware dot org [this message]
2024-01-13 18:33 ` [Bug varobj/23367] " ssbssa 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).