From: Tom Tromey <tromey@adacore.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle encoding failures in Windows thread names
Date: Thu, 02 Jun 2022 08:33:02 -0600 [thread overview]
Message-ID: <878rqf3zkx.fsf@tromey.com> (raw)
In-Reply-To: <6f7e3db5-76f4-e21d-edbd-2cd1993a7bdd@dronecode.org.uk> (Jon Turney's message of "Thu, 2 Jun 2022 15:19:21 +0100")
>>>>> "Jon" == Jon Turney <jon.turney@dronecode.org.uk> writes:
Jon> This is probably wrong on Cygwin (as the target encoding should be
Jon> Cygwin's conception of the locale, not the Windows codepage).
If there's some way for gdb to know the locale of the inferior, I guess
we could use that here. I don't have Cygwin and so I can't test it or
anything, but if I knew what to do I could try to write a patch for
someone else to test.
Tom
next prev parent reply other threads:[~2022-06-02 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 14:39 Tom Tromey
2022-04-21 15:47 ` Eli Zaretskii
2022-04-26 18:53 ` Tom Tromey
2022-06-02 14:19 ` Jon Turney
2022-06-02 14:33 ` Tom Tromey [this message]
2022-06-02 19:29 ` Jon Turney
2022-06-03 16:19 ` Tom Tromey
2022-06-02 16:07 ` Eli Zaretskii
2022-06-02 19:29 ` Jon Turney
2022-06-03 5:28 ` 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=878rqf3zkx.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jon.turney@dronecode.org.uk \
/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).