From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: mark.kettenis@xs4all.nl, brobecker@adacore.com,
bauerman@br.ibm.com, andreolb@gmail.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Tue, 17 Mar 2009 22:12:00 -0000 [thread overview]
Message-ID: <uiqm7rekb.fsf@gnu.org> (raw)
In-Reply-To: <m31vsvncks.fsf@fleche.redhat.com>
> Cc: brobecker@adacore.com, bauerman@br.ibm.com, andreolb@gmail.com, gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 17 Mar 2009 14:01:23 -0600
>
> *** Changes since GDB 6.8
>
> +* GDB now has support for multi-byte and wide character sets on the
> +target. Strings whose character type is wchar_t, char16_t, or
> +char32_t are now correctly printed. GDB supports wide- and unicode-
> +literals in C, that is, L'x', L"string", u'x', u"string", U'x', and
> +U"string" syntax. And, GDB allows the "%ls" and "%lc" formats in
> +`printf'.
> +
> * GDB now supports automatic retrieval of shared library files from
> remote targets. To use this feature, specify a system root that begins
> with the `remote:' prefix, either via the `set sysroot' command or via
> @@ -182,6 +189,11 @@ set target-async
> with GDB while the target is running. "show target-async" displays the
> current state of asynchronous execution of the target.
>
> +set target-wide-charset
> +show target-wide-charset
> + The target-wide-charset is the name of the character set that GDB
> + uses when printing characters whose type is wchar_t.
> +
This text is okay, but I think we should mention that libiconv is
required for a _real_ support of these features.
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 5b3c50b..7a49aea 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
This part is OK, thanks.
next prev parent reply other threads:[~2009-03-17 22:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30 ` Daniel Jacobowitz
2009-03-11 17:09 ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13 ` Tom Tromey
2009-03-11 18:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29 ` Thiago Jung Bauermann
2009-03-11 22:25 ` Tom Tromey
2009-03-12 1:11 ` Tom Tromey
2009-03-13 23:37 ` Joel Brobecker
2009-03-13 23:38 ` Joel Brobecker
2009-03-14 1:41 ` Tom Tromey
2009-03-14 0:10 ` Mark Kettenis
2009-03-17 20:06 ` Tom Tromey
2009-03-17 22:12 ` Eli Zaretskii [this message]
2009-03-18 3:07 ` Tom Tromey
2009-03-18 4:20 ` Eli Zaretskii
2009-03-18 17:11 ` Tom Tromey
2009-03-18 20:30 ` Eli Zaretskii
2009-03-18 0:46 ` Joel Brobecker
2009-03-18 1:14 ` Tom Tromey
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=uiqm7rekb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreolb@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.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