From: Tom Tromey <tom@tromey.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>,
gdb@sourceware.org
Subject: Re: Thread names and non-ASCII characters
Date: Thu, 19 Dec 2019 18:25:00 -0000 [thread overview]
Message-ID: <87bls4b2b7.fsf@tromey.com> (raw)
In-Reply-To: <7DCA8806-7F56-4D41-84F1-8264C897FB8A@comcast.net> (Paul Koning's message of "Thu, 19 Dec 2019 12:54:56 -0500")
>>>>> "Paul" == Paul Koning <paulkoning@comcast.net> writes:
>> Converting to the host charset is probably the thing to do.
Paul> Host charset, or target charset? I would assume target since
Paul> we're talking about threads on the target.
In this case it sounded like the charset on the target is known to be
UTF-16, but to display in gdb it has to be converted from that to the
host charset.
For Linux, we should probably convert from the target charset to the
host charset; though this seems a little odd, in that I think the kernel
enforces a (short) length limit on thread names, and anybody using
non-ASCII risks having the name be cut off in the middle of a UTF-8
sequence.
Tom
next prev parent reply other threads:[~2019-12-19 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 15:17 Eli Zaretskii
2019-12-19 17:22 ` Tom Tromey
2019-12-19 17:55 ` Paul Koning
2019-12-19 18:25 ` Tom Tromey [this message]
2019-12-19 19:02 ` Eli Zaretskii
2019-12-19 18:59 ` Eli Zaretskii
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=87bls4b2b7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=paulkoning@comcast.net \
/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