public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, simonsobisch@web.de,
	 Tom Tromey <tom@tromey.com>,
	Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v4 7/8] GDB: Add a character string limiting option
Date: Thu, 10 Mar 2022 12:25:24 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.20.2203101218010.11552@tpp.orcam.me.uk> (raw)
In-Reply-To: <83a6dydntg.fsf@gnu.org>

On Thu, 10 Mar 2022, Eli Zaretskii wrote:

> >  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?

 Not directly, but as I understand it it affects the interpretation of a 
byte stream retrieved as a character string (null-terminated in the case 
of C/C++, but possibly represented differently with other languages such 
as Pascal).  So the same byte stream may have a different character count 
depending on the encoding chosen.

  Maciej

  reply	other threads:[~2022-03-10 12:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 19:17 [PATCH v4 0/8] gdb: split array and string limiting options Maciej W. Rozycki
2022-03-09 19:17 ` [PATCH v4 1/8] GDB: Remove extraneous full stops from `set' command error messages Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 2/8] GDB/Python: Use None for `var_zuinteger_unlimited' value set to `unlimited' Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 3/8] GDB: Add `NUMBER' completion to `set' integer commands Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 4/8] GDB/testsuite: Tighten `set print elements' error check Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 5/8] GDB/testsuite: Add coverage for `print -elements' command Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 6/8] GDB: Allow arbitrary keywords in integer set commands Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 7/8] GDB: Add a character string limiting option Maciej W. Rozycki
2022-03-09 19:51   ` Eli Zaretskii
2022-03-09 20:40     ` Maciej W. Rozycki
2022-03-10  0:03       ` Maciej W. Rozycki
2022-03-10  6:35         ` Eli Zaretskii
2022-03-10  6:28       ` Eli Zaretskii
2022-03-10 10:08         ` Maciej W. Rozycki
2022-03-10 11:55           ` Eli Zaretskii
2022-03-10 12:25             ` Maciej W. Rozycki [this message]
2022-03-10 17:15           ` Tom Tromey
2022-03-30 10:38             ` Maciej W. Rozycki
2022-03-30 13:15               ` Pedro Alves
2022-03-30 14:17                 ` Maciej W. Rozycki
2022-03-09 19:18 ` [PATCH v4 8/8] GDB/testsuite: Expand for character string limiting options Maciej W. Rozycki
2022-03-09 19:47 ` [PATCH v4 0/8] gdb: split array and " Simon Sobisch

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=alpine.DEB.2.20.2203101218010.11552@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simonsobisch@web.de \
    --cc=tom@tromey.com \
    /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).