public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tom@tromey.com>,
	simonsobisch@web.de,  Andrew Burgess <aburgess@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v4 7/8] GDB: Add a character string limiting option
Date: Wed, 30 Mar 2022 15:17:02 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2203301502500.11552@tpp.orcam.me.uk> (raw)
In-Reply-To: <94f11eb5-00c4-d3f4-6ca3-400ffc454755@palves.net>

On Wed, 30 Mar 2022, Pedro Alves wrote:

> > Though I'd yet have to figure out how to use the syntax quoted in NEWS in 
> > a meaningful manner, and an artificial program may also be required, 
> > because:
> > 
> > (gdb) print L"foobar"
> > No type named wchar_t.
> > (gdb) print u"foobar"
> > No type named char16_t.
> > (gdb) print U"foobar"
> > No type named char32_t.
> > (gdb) 
> > 
> > though I guess the data types do not actually have to be system-supplied, 
> > and it will be enough if they are reasonably defined.
> 
> It will work without a program if you switch to C++ beforehand, with "set language c++",
> because wchar_t/char16_t/char32_t are built-in types in C++.

 Excellent, and indeed it does the right thing too:

(gdb) set language c++
(gdb) print L"foobar"
$1 = L"foobar"
(gdb) print u"foobar"
$2 = u"foobar"
(gdb) print U"foobar"
$3 = U"foobar"
(gdb) set print characters 4
(gdb) print L"foobar"
$4 = L"foob"...
(gdb) print u"foobar"
$5 = u"foob"...
(gdb) print U"foobar"
$6 = U"foob"...
(gdb) 

exactly as documented.  Thanks for the hint!

  Maciej

  reply	other threads:[~2022-03-30 14:17 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
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 [this message]
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.2203301502500.11552@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --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).