From: Simon Sobisch <simonsobisch@gnu.org>
To: gdb@sourceware.org
Subject: UnicodeDecodeError on gdb.execute
Date: Wed, 3 Nov 2021 21:50:03 +0100 [thread overview]
Message-ID: <33ec492b-3689-80fd-ca78-a4e2e69b9180@gnu.org> (raw)
In-Reply-To: <60c53fa8bf160533a2eddf1da280eb50c7461a6a.camel@fit.cvut.cz>
For some special file I need to look at the source code from within the
GDB extension.
I did this with the reasonable and obious
output = gdb.execute("list *" + hex(sal.pc), False, True)
(and get more lines with a follow-up "list" [not all are needed,
otherwise the gdb.parameter("listsize") could be adjusted).
I _think_ the problem I expect now is because of a system with Python3
which has default utf8 encoding, but it _may_ was also in before:
There's a python exception UnicodeDecodeError in this line whenever it
contains "extended" ascii.
"list" in GDB shows the code correctly; also
(gdb) py gdb.execute("list 14")
shows the correct text, but as soon as python has to internally decode
it to store a string:
(gdb) py gdb.execute("list 14", False, True)
Traceback (most recent call last):
File "<string>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in
position 18: invalid start byte
Error while executing Python code.
is there any way I could adjust the encoding used for storing
gdb.execute as string?
Is there a reason that this isn't by default set to match
gdb.target_charset() ?
Thanks for insights to this issue, too,
Simon
next prev parent reply other threads:[~2021-11-03 20:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 16:40 How to create new mi commands via python / get current interpreter in python Simon Sobisch
2021-11-02 16:56 ` Jan Vrany
2021-11-02 19:11 ` Simon Sobisch
2021-11-03 9:06 ` Jan Vrany
2021-11-05 18:51 ` Jan Vrany
2021-11-05 21:18 ` feature branch for creating MI commands with python (was: How to create new mi commands via python / get current interpreter in python) Simon Sobisch
2021-11-23 12:29 ` Jan Vrany
2021-11-23 12:48 ` Lancelot SIX
2021-11-23 16:28 ` Jan Vrany
2021-11-03 16:31 ` How to get the full source location of a frame via python Simon Sobisch
2021-11-03 20:07 ` Jan Vrany
2021-11-03 20:35 ` Simon Sobisch
2021-11-03 20:50 ` Simon Sobisch [this message]
2021-11-03 21:55 ` Is "forward-search" also possible case insensitive? Simon Sobisch
2021-11-05 9:14 ` Is there a way to know about current "until"/"advance" execution? Simon Sobisch
2021-11-22 14:54 ` Is there a way to get a function's end address other than `disassemble`? Simon Sobisch
2021-11-22 15:14 ` Andreas Schwab
2021-11-22 15:17 ` Simon Sobisch
2021-11-25 19:28 ` Broken source view with Pygments and non-UTF-8 encoded source Simon Sobisch
2021-11-26 11:16 ` Andrew Burgess
2021-11-26 13:39 ` Andrew Burgess
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=33ec492b-3689-80fd-ca78-a4e2e69b9180@gnu.org \
--to=simonsobisch@gnu.org \
--cc=gdb@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).