From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-47360-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18692 invoked by alias); 19 Dec 2019 18:59:21 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 18684 invoked by uid 89); 19 Dec 2019 18:59:21 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-3.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=
X-HELO: eggs.gnu.org
Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 18:59:20 +0000
Received: from fencepost.gnu.org ([2001:470:142:3::e]:38792)	by eggs.gnu.org with esmtp (Exim 4.71)	(envelope-from <eliz@gnu.org>)	id 1ii114-0003uF-MN; Thu, 19 Dec 2019 13:59:18 -0500
Received: from [176.228.60.248] (port=3074 helo=home-c4e4a596f7)	by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)	(Exim 4.82)	(envelope-from <eliz@gnu.org>)	id 1ii113-0000gK-He; Thu, 19 Dec 2019 13:59:18 -0500
Date: Thu, 19 Dec 2019 18:59:00 -0000
Message-Id: <83lfr816rl.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
CC: gdb@sourceware.org
In-reply-to: <87lfr8cjsi.fsf@tromey.com> (message from Tom Tromey on Thu, 19	Dec 2019 10:22:21 -0700)
Subject: Re: Thread names and non-ASCII characters
References: <831rt02vlb.fsf@gnu.org> <87lfr8cjsi.fsf@tromey.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00043.txt.bz2

> From: Tom Tromey <tom@tromey.com>
> Cc: gdb@sourceware.org
> Date: Thu, 19 Dec 2019 10:22:21 -0700
> 
> Eli> I'm asking because Windows 10 introduces a new API for setting and
> Eli> getting a thread's name, but this API wants a UTF-16 encoded string,
> Eli> so if we want to use it, we need to decide from/to what encoding to
> Eli> convert to/from UTF-16.
> 
> Converting to the host charset is probably the thing to do.
> If the host charset is decided incorrectly, then enhancing charset.c to
> choose a better one would help in other places as well.
> 
> convert_between_encodings can be used to do the translation.

OK, thanks for the pointers.  I hope to find some time to do this
soonish.