From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30690 invoked by alias); 19 Dec 2019 17:55:06 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 30358 invoked by uid 89); 19 Dec 2019 17:55:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=H*m:net, HX-Languages-Length:970, H*MI:sk:87lfr8c, H*MI:sk:831rt02 X-HELO: resqmta-po-06v.sys.comcast.net Received: from resqmta-po-06v.sys.comcast.net (HELO resqmta-po-06v.sys.comcast.net) (96.114.154.165) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 17:55:05 +0000 Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-06v.sys.comcast.net with ESMTP id hzPOiFIXq1p3Ci00siYV0Z; Thu, 19 Dec 2019 17:55:02 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1576778102; bh=gUwRwv37LTtafxC8KDL+vHC2EUoxZxBXSMBbb0f9ZxM=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=MXpQ+Z24SIxSpjABHu54hUsKbCqVESKXLMmOfosnqVD/RPU8bB+0JbmQUQ3EMYzXz OovtLkz5VSwDLL/quNlMmzAGPsDMNPfsLXi+rANhjyiDYkr4K0XNR2l70NDxFFOlFD NYyuxe72KQYuJuwP3XXwB9t1zl4zUrXPBKHVqeVTGujGTIBf5LfyGs1BPz2aZP41KG meQlOZr2eyyew+w8M2haCpqJSx1rT1Ki7NtvJ9dCkEOdUijZIBTwlVAxDw0hbn5Lr8 ZUW2KfhnZ4wEEVmO+KGpsDODp3OMXOrrUcNzaqohhx9pi9OPMuzmpmDjfjSmm6HyLz t388EO9hSIxhg== Received: from pkoning.akdesign.com ([73.60.223.101]) by resomta-po-04v.sys.comcast.net with ESMTPA id i00niUoiblklHi00riYCPg; Thu, 19 Dec 2019 17:55:02 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedufedrvdduuddguddthecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpefrrghulhcumfhonhhinhhguceophgruhhlkhhonhhinhhgsegtohhmtggrshhtrdhnvghtqeenucfkphepjeefrdeitddrvddvfedruddtudenucfrrghrrghmpehhvghlohepphhkohhnihhnghdrrghkuggvshhighhnrdgtohhmpdhinhgvthepjeefrdeitddrvddvfedruddtuddpmhgrihhlfhhrohhmpehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvthdprhgtphhtthhopehtohhmsehtrhhomhgvhidrtghomhdprhgtphhtthhopegvlhhiiiesghhnuhdrohhrghdprhgtphhtthhopehguggssehsohhurhgtvgifrghrvgdrohhrghenucevlhhushhtvghrufhiiigvpedt X-Xfinity-VMeta: sc=-100.00;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Thread names and non-ASCII characters From: Paul Koning In-Reply-To: <87lfr8cjsi.fsf@tromey.com> Date: Thu, 19 Dec 2019 17:55:00 -0000 Cc: Eli Zaretskii , gdb@sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: <7DCA8806-7F56-4D41-84F1-8264C897FB8A@comcast.net> References: <831rt02vlb.fsf@gnu.org> <87lfr8cjsi.fsf@tromey.com> To: Tom Tromey X-SW-Source: 2019-12/txt/msg00041.txt.bz2 > On Dec 19, 2019, at 12:22 PM, Tom Tromey wrote: >=20 >>>>>> "Eli" =3D=3D Eli Zaretskii writes: >=20 > Eli> Can someone tell what GDB assumes to be the character encoding used = by > Eli> thread names we get from the system APIs (such as pthread_getname_np= )? > Eli> It sounds like we assume the host character set, since the functions > Eli> used to display the thread name don't perform any encoding conversio= n. > Eli> Is my understanding correct? >=20 > Yes, I believe so. >=20 > 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. >=20 > Converting to the host charset is probably the thing to do. Host charset, or target charset? I would assume target since we're talking= about threads on the target. paul