From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92])
 by sourceware.org (Postfix) with ESMTPS id EDDEE3858C20
 for <gdb-patches@sourceware.org>; Thu, 10 Mar 2022 11:55:28 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EDDEE3858C20
Received: from [2001:470:142:3::e] (port=54604 helo=fencepost.gnu.org)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1nSHOC-00044i-8h; Thu, 10 Mar 2022 06:55:28 -0500
Received: from [87.69.77.57] (port=1108 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1nSHOB-00064S-MC; Thu, 10 Mar 2022 06:55:28 -0500
Date: Thu, 10 Mar 2022 13:55:23 +0200
Message-Id: <83a6dydntg.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org, simonsobisch@web.de, tom@tromey.com,
 aburgess@redhat.com
In-Reply-To: <alpine.DEB.2.20.2203100950540.11552@tpp.orcam.me.uk>
 (macro@embecosm.com)
Subject: Re: [PATCH v4 7/8] GDB: Add a character string limiting option
References: <alpine.DEB.2.20.2203031442040.11552@tpp.orcam.me.uk>
 <alpine.DEB.2.20.2203091620080.11552@tpp.orcam.me.uk>
 <83o82eewgh.fsf@gnu.org>
 <alpine.DEB.2.20.2203092025330.11552@tpp.orcam.me.uk>
 <83mthye2yu.fsf@gnu.org>
 <alpine.DEB.2.20.2203100950540.11552@tpp.orcam.me.uk>
X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF,
 RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gdb-patches@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2022 11:55:30 -0000

> Date: Thu, 10 Mar 2022 10:08:03 +0000 (GMT)
> From: "Maciej W. Rozycki" <macro@embecosm.com>
> cc: gdb-patches@sourceware.org, simonsobisch@web.de, 
>     Tom Tromey <tom@tromey.com>, Andrew Burgess <aburgess@redhat.com>
> 
>  NB is there a way to orchestrate a wide character string in a way that 
> wouldn't show gibberish on a plain-ASCII terminal (both in the source form 
> and in output) so as to get this feature covered in the test suite?  I'm 
> not an expert on character encodings beyond ASCII/8-bit.  I can see we 
> have a bunch of settings related to this:
> 
> (gdb) show charset
> The host character set is "auto; currently ANSI_X3.4-1968".
> The target character set is "auto; currently ANSI_X3.4-1968".
> The target wide character set is "auto; currently UTF-32".

Does this affect how we count characters for the purpose of the patch
we are discussing?