public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "noamraph at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/10611] New: MI vars with children in pretty-printer don't get printed correctly Date: Sun, 06 Sep 2009 13:05:00 -0000 [thread overview] Message-ID: <20090906130545.10611.noamraph@gmail.com> (raw) Hello, I pulled the most recent version of the archer-tromey-python branch. Bug 10584 was indeed fixed. However, if I add children to the pretty-printer, the MI value gets totally corrupted: p x $1 = MyInt: 3 = { # I stripped things. [0] = 1, [1] = 2, [2] = 3 } ^done (gdb) -var-create x * x ^done,name="x",numchild="0",value="{...}",type="MyInt",thread-id="1",has_more="1" (The pretty printer in bug.py just adds constant three children, as you can see.) To recreate, download bug.c and bug.py. Compile bug.c. Run: gdb --int mi2 a.out -enable-pretty-printing python execfile('bug.py') b main r n -var-create x * x And you get the response above. Thanks, Noam -- Summary: MI vars with children in pretty-printer don't get printed correctly Product: gdb Version: archer Status: UNCONFIRMED Severity: normal Priority: P2 Component: mi AssignedTo: unassigned at sourceware dot org ReportedBy: noamraph at gmail dot com CC: gdb-prs at sourceware dot org http://sourceware.org/bugzilla/show_bug.cgi?id=10611 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-09-06 13:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-06 13:05 noamraph at gmail dot com [this message] 2009-09-06 13:06 ` [Bug mi/10611] " noamraph at gmail dot com 2009-09-06 13:06 ` noamraph at gmail dot com 2009-09-08 19:14 ` tromey at redhat dot com 2009-09-09 6:52 ` noamraph at gmail dot com
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=20090906130545.10611.noamraph@gmail.com \ --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).