public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11948] lazy_string should be lazier
Date: Fri, 27 Aug 2010 09:37:00 -0000 [thread overview]
Message-ID: <20100827093731.16844.qmail@sourceware.org> (raw)
In-Reply-To: <20100826205357.11948.tromey@redhat.com>
------- 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.
next prev parent reply other threads:[~2010-08-27 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 20:53 [Bug python/11948] New: " tromey at redhat dot com
2010-08-27 9:37 ` andre dot poenitz at nokia dot com [this message]
2010-08-28 8:06 ` [Bug python/11948] " niko dot sams at gmail dot com
[not found] <bug-11948-4717@http.sourceware.org/bugzilla/>
2010-10-14 19:42 ` tromey at redhat dot com
2010-10-18 19:44 ` 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=20100827093731.16844.qmail@sourceware.org \
--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).