From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA] Fix typo in type of parameter "w" in print_wchar...
Date: Sat, 25 Apr 2009 00:37:00 -0000 [thread overview]
Message-ID: <20090425003658.GA32745@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
I think this is the last issue I've found so far with character set
conversions and printing...
This one occurs on AIX while trying to print a simple ascii string.
The output looks like this:
(gdb) p __gnat_version
$3 = "
The problem turned out to be pretty straightforward, once I got to
understand how things are supposed to work.
Basically, for every character in our string, we call print_wchar
to push the equivalent wchar on our itermediate wchar buffer.
The issue is that we had the wrong type for the wchar (gdb_wint_t
instead of gdb_wchar_t). gdb_wint_t is 4bytes long whereas gdb_wchar_t
is 2 bytes long. So when we do the pushing:
obstack_grow (output, &w, sizeof (gdb_wchar_t));
We only push 2 bytes of the 4 bytes that w got accidently promoted to.
On ppc-aix, it's big endian, so we end up always pushing zeros...
2009-04-24 Joel Brobecker <brobecker@adacore.com>
* c-lang.c (print_wchar): Use the correct type for parameter "w".
I'm currently testing the patch on x86_64-linux...
--
Joel
[-- Attachment #2: c-lang.diff --]
[-- Type: text/x-diff, Size: 453 bytes --]
diff --git a/gdb/c-lang.c b/gdb/c-lang.c
index 027e9b2..5fe04de 100644
--- a/gdb/c-lang.c
+++ b/gdb/c-lang.c
@@ -156,7 +156,7 @@ append_string_as_wide (const char *string, struct obstack *output)
escapes across calls. */
static void
-print_wchar (gdb_wint_t w, const gdb_byte *orig, int orig_len,
+print_wchar (gdb_wchar_t w, const gdb_byte *orig, int orig_len,
int width, struct obstack *output, int quoter,
int *need_escapep)
{
next reply other threads:[~2009-04-25 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 0:37 Joel Brobecker [this message]
2009-04-25 8:50 ` Mark Kettenis
2009-05-07 18:38 ` Joel Brobecker
2009-05-07 18:53 ` Mark Kettenis
2009-05-07 20:48 ` Joel Brobecker
2009-05-12 8:06 ` Joel Brobecker
2009-05-13 9:43 ` 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=20090425003658.GA32745@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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