This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/11948] lazy_string should be lazier
- From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 27 Aug 2010 09:37:31 -0000
- Subject: [Bug python/11948] lazy_string should be lazier
- References: <20100826205357.11948.tromey@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From andre dot poenitz at nokia dot com 2010-08-27 09:37 -------
I would also be nice if there was a way to generate "robust" output (preferably
7 bit clean data, like hex-encoded contents) directly from a lazy string.
Maybe that this can be combined with the "Easier and more stubborn MI memory
read commands. " change to be robust even when the inferior memory is not
accessible. In this case, the "hex encoding" could e.g. use "??" to signify an
inaccessible byte.
That would make a lazy string to a kind of "handle" to inferior memory, string
data or not, that would be more flexible to use.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11948
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.