Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Klaus-Georg Adams <Klaus-Georg.Adams@sap.com>, gdb@sources.redhat.com
Subject: Re: displaying wchar_t in gdb
Date: Sat, 24 Nov 2001 22:42:00 -0000	[thread overview]
Message-ID: <87k7w9d0n8.fsf@creche.redhat.com> (raw)
In-Reply-To: Eli Zaretskii's message of "Thu, 29 Nov 2001 10:18:43 +0200 (IST)"

>>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> writes:

Eli> Risky assumptions, both of them (IMHO).  For example, GDB can be
Eli> conceivably built with libiconv, but you cannot force the
Eli> debuggee to be built with it.

I don't think the debuggee would need iconv.  GDB would fetch raw
bytes from the inferior, and then transform them to the appropriate
output encoding using the host iconv.

>> For wchar_t I don't think you need a new `print' format (well maybe to
>> specify the encoding).  I think a wchar_t string could be printed
>> based solely on the type, the way we print a char* string right now.

Eli> I think you need a format because a buffer can be declared
Eli> `unsigned char *' even though it holds wide characters.

There's always `p (wchar_t *) buf'.
I already use this idiom with ordinary char* strings on occasion.

Tom


WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Klaus-Georg Adams <Klaus-Georg.Adams@sap.com>, gdb@sources.redhat.com
Subject: Re: displaying wchar_t in gdb
Date: Thu, 29 Nov 2001 08:04:00 -0000	[thread overview]
Message-ID: <87k7w9d0n8.fsf@creche.redhat.com> (raw)
Message-ID: <20011129080400.RXxH5sHW00pUt3NW3RJUOdXrnyiOVS8Ay_X2dnMjmQ8@z> (raw)
In-Reply-To: <Pine.SUN.3.91.1011129101817.10998J-100000@is>

>>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> writes:

Eli> Risky assumptions, both of them (IMHO).  For example, GDB can be
Eli> conceivably built with libiconv, but you cannot force the
Eli> debuggee to be built with it.

I don't think the debuggee would need iconv.  GDB would fetch raw
bytes from the inferior, and then transform them to the appropriate
output encoding using the host iconv.

>> For wchar_t I don't think you need a new `print' format (well maybe to
>> specify the encoding).  I think a wchar_t string could be printed
>> based solely on the type, the way we print a char* string right now.

Eli> I think you need a format because a buffer can be declared
Eli> `unsigned char *' even though it holds wide characters.

There's always `p (wchar_t *) buf'.
I already use this idiom with ordinary char* strings on occasion.

Tom


  parent reply	other threads:[~2001-11-29 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 16:57 Klaus-Georg Adams
2001-11-26  1:16 ` Klaus-Georg Adams
2001-11-26  1:29 ` Eli Zaretskii
2001-11-13 21:23   ` Eli Zaretskii
2001-11-26  1:59   ` Klaus-Georg Adams
2001-11-13 21:28     ` Klaus-Georg Adams
2001-11-26  4:11     ` Eli Zaretskii
2001-11-13 23:51       ` Eli Zaretskii
2001-11-22  9:19       ` LeakyStain
2001-11-28 15:38         ` LeakyStain
2001-11-22 14:30       ` Tom Tromey
2001-11-28 16:02         ` Tom Tromey
2001-11-29  0:19         ` Eli Zaretskii
2001-11-23 13:27           ` Eli Zaretskii
2001-11-24 22:42           ` Tom Tromey [this message]
2001-11-29  8:04             ` Tom Tromey
2001-11-25 10:38 Klaus-Georg Adams
2001-11-25 10:44 ` Arnaud Charlet
2001-11-30  2:22   ` Arnaud Charlet
2001-11-25 12:10 ` Paul Hilfinger
2001-11-30  3:36   ` Paul Hilfinger
2001-11-30  2:15 ` Klaus-Georg Adams
2001-11-30  2:25 ` Joel Brobecker
2001-11-25 10:54   ` Joel Brobecker

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=87k7w9d0n8.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Klaus-Georg.Adams@sap.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.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