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/10615] New: Nested structs don't get updated in MI Date: Tue, 08 Sep 2009 07:33:00 -0000 [thread overview] Message-ID: <20090908073304.10615.noamraph@gmail.com> (raw) Hello, Thankfully, Tom fixed bug 10584. However, it seems that members of structs which are members of pretty-printed variables still don't get updated. To recreate: Download bug.c, bug.py. > gcc -g -o bug bug.c > gdb --int mi2 --nx bug > -enable-pretty-printing > python execfile('bug.py') > b main > r # Initialize m to {{0},0} > n # Do what a standard UI is expected to do to print the m variable # Its structure is: { {int a; int b;} s; int x; } > -var-create m * m > -var-list-children m > -var-evaluate-expression m.s > -var-list-children m.s > -var-evaluate-expression m.s.a > -var-evaluate-expression m.s.b > -var-evaluate-expression m.x # Modify m.s.a > n # Check if something was updated > -var-update * ^done,changelist=[] # Oops. Thanks, Noam -- Summary: Nested structs don't get updated in MI 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,tromey at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=10615 ------- 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-08 7:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-08 7:33 noamraph at gmail dot com [this message] 2009-09-08 7:33 ` [Bug mi/10615] " noamraph at gmail dot com 2009-09-08 7:34 ` noamraph at gmail dot com 2009-09-08 20:01 ` tromey at redhat dot com 2009-09-09 16:08 ` tromey at redhat 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=20090908073304.10615.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).