public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/18282] Pretty Printers - unable to create variable object (string value from children()) Date: Thu, 31 Aug 2023 16:13:19 +0000 [thread overview] Message-ID: <bug-18282-4717-TbAWbRGEwl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18282-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18282 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #5 from Tom Tromey <tromey at sourceware dot org> --- This seems to be two different bugs. First, if children returns strings, they don't seem to appear. I get this from my test: ^done,numchild="5",children=[child={name="tval.1",exp="1",numchild="8",value="[8]",type="char [8]"},child={name="tval.2",exp="2",numchild="7",value="[7]",type="char [7]"},child={name="tval.3",exp="3",numchild="7",value="[7]",type="char [7]"},child={name="tval.4",exp="4",numchild="7",value="[7]",type="char [7]"},child={name="tval.5",exp="5",numchild="6",value="[6]",type="char [6]"}],has_more="0" The string values don't appear at all, instead for some reason we're getting map "indices". Second, the name returned by the printer doesn't necessarily correspond to any kind of sub-object. This is the part that is bug#17529. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-31 16:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-20 14:32 [Bug mi/18282] New: Pretty Printers - prints string value as char[] from children() david.docteur at intel dot com 2015-04-20 14:40 ` [Bug mi/18282] Pretty Printers - unable to create variable object (string value from children()) david.docteur at intel dot com 2015-04-20 15:37 ` xdje42 at gmail dot com 2015-04-21 13:03 ` david.docteur at intel dot com 2021-07-02 20:32 ` alex.zhigay at yandex dot ru 2023-08-31 16:13 ` tromey at sourceware dot org [this message] 2023-08-31 17:17 ` [Bug varobj/18282] " tromey at sourceware dot org 2023-08-31 17:54 ` tromey at sourceware dot org 2023-08-31 18:21 ` tromey at sourceware dot org 2023-09-07 20:06 ` cvs-commit at gcc dot gnu.org 2023-09-07 20:07 ` 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: 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=bug-18282-4717-TbAWbRGEwl@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).