This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/11482] Side effect of set print address on python API
- From: "michel dot metzger at st dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 14 Apr 2010 21:07:58 -0000
- Subject: [Bug python/11482] Side effect of set print address on python API
- References: <20100409172931.11482.michel.metzger@st.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From michel dot metzger at st dot com 2010-04-14 21:07 -------
I understand, but I still think that the user, with the python API, should still
be able to get the value of a pointer regardless of the state of set print
address. What if he doesn't want to print it? In my case I use it as an index in
an internal table.
Developers of new commands in python should make sure they follow the rules set
by commands like set print address.
I hope this clarify things :)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11482
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.