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 gdb/10584] New: MI vars with Python pretty-printers don't get updated
Date: Tue, 01 Sep 2009 08:16:00 -0000 [thread overview]
Message-ID: <20090901081610.10584.noamraph@gmail.com> (raw)
Hello,
If I create a Python pretty-printer, it doesn't get updated in GUI using gdb.
This is because the MI var doesn't get updated. To recreate:
Download bug.c, bug.py which I will attach in a minute.
> gcc -g bug.c
> gdb --int mi2
(gdb) python execfile("bug.py") # Install pretty-printer for type "MyInt"
(gdb) break main
(gdb) run
(gdb) next # do x = 3
(gdb) -var-create x * x
(gdb) next # x = 5
(gdb) -var-update * # Doesn't report x changing.
This was tested on a current CVS: 6.8.50.20090831
Thanks,
Noam
--
Summary: MI vars with Python pretty-printers don't get updated
Product: gdb
Version: 6.8
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
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=10584
------- 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-01 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 8:16 noamraph at gmail dot com [this message]
2009-09-01 8:16 ` [Bug gdb/10584] " noamraph at gmail dot com
2009-09-01 8:17 ` noamraph at gmail dot com
2009-09-01 9:12 ` noamraph at gmail dot com
2009-09-01 9:13 ` noamraph at gmail dot com
2009-09-01 9:14 ` noamraph at gmail dot com
2009-09-01 16:06 ` tromey at redhat dot com
2009-09-03 7:45 ` noamraph at gmail dot com
2009-09-03 13:26 ` noamraph at gmail dot com
2009-09-03 13:37 ` noamraph at gmail dot com
2009-09-03 16:15 ` tromey at redhat dot com
2009-09-03 18:14 ` 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=20090901081610.10584.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: 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).