public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/17138] C strings, gdb.Value.__str__, and Python 3
Date: Wed, 13 Sep 2023 14:47:40 +0000 [thread overview]
Message-ID: <bug-17138-4717-nfjjLyPia0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17138-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17138
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I think this area has been cleaned up somewhat and now this bug
is obsolete.
Python 2 is no longer supported.
Value.string does try to make a Python string and will fail if
the encoding is wrong. It works like Python decoders, though.
Value.lazy_string can be used from pretty-printers to defer
decisions to gdb's internal decoding code. When printing
this can handle possibly-incorrect contents.
Memory can be read directly now and returned as a memoryview
object. This avoids all encoding problems and lets code
deal with just bytes.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-09-13 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 2:47 [Bug python/17138] New: " naesten at gmail dot com
2014-07-10 4:59 ` [Bug python/17138] " b.r.longbons at gmail dot com
2023-09-13 14:47 ` tromey at sourceware dot org [this message]
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=bug-17138-4717-nfjjLyPia0@http.sourceware.org/bugzilla/ \
--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).