From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4166 invoked by alias); 19 Dec 2019 18:25:20 -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 4158 invoked by uid 89); 19 Dec 2019 18:25:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=H*i:sk:7DCA880, H*f:sk:7DCA880 X-HELO: gateway23.websitewelcome.com Received: from gateway23.websitewelcome.com (HELO gateway23.websitewelcome.com) (192.185.50.250) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 18:25:18 +0000 Received: from cm13.websitewelcome.com (cm13.websitewelcome.com [100.42.49.6]) by gateway23.websitewelcome.com (Postfix) with ESMTP id A90033D37 for ; Thu, 19 Dec 2019 12:25:17 -0600 (CST) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id i0U9ivvzJ3Qi0i0U9inC20; Thu, 19 Dec 2019 12:25:17 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=BU6EYI0w9l9qSxA66rRdHVuREmzmOhBI0QweQhAbjOI=; b=hiXoi1TubJCY8XZRsjT4lKRBk5 uYYY+KSV1wN7ss23j+/+uoHbm7+81Dh7R0tONzbdIV3JOAGlwSFRTMUDKo7OaLsz2nNGEOHp1UHsh 0kTI9IUYab7sWJNl6qD66WWPN; Received: from 75-166-123-50.hlrn.qwest.net ([75.166.123.50]:37504 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1ii0U9-0018ve-E3; Thu, 19 Dec 2019 11:25:17 -0700 From: Tom Tromey To: Paul Koning Cc: Tom Tromey , Eli Zaretskii , gdb@sourceware.org Subject: Re: Thread names and non-ASCII characters References: <831rt02vlb.fsf@gnu.org> <87lfr8cjsi.fsf@tromey.com> <7DCA8806-7F56-4D41-84F1-8264C897FB8A@comcast.net> Date: Thu, 19 Dec 2019 18:25:00 -0000 In-Reply-To: <7DCA8806-7F56-4D41-84F1-8264C897FB8A@comcast.net> (Paul Koning's message of "Thu, 19 Dec 2019 12:54:56 -0500") Message-ID: <87bls4b2b7.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-12/txt/msg00042.txt.bz2 >>>>> "Paul" == Paul Koning 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