From: J K <ellips@yahoo.com>
To: gdb@sources.redhat.com
Subject: gdb print /x always big endian order?
Date: Thu, 05 Feb 2004 18:00:00 -0000 [thread overview]
Message-ID: <20040205180043.68640.qmail@web13509.mail.yahoo.com> (raw)
Hello,
I've used a simple code to examine the storage
of a short on a big and little endian machine.
It seems in GNU gdb Red Hat Linux (5.1-1) when
I do a print /x the order is Big Endian regardless
of the host architecture. Just wondering if this
is expected, I didn't see anything in the docs.
short short_val = 31415;
unsigned char buff[8];
memcpy(buff,&short_val,2);
printf("Short bytes 0x%x 0x%x\n",buff[0],buff[1]);
on Little Endian machine:
Short bytes 0xb7 0x7a
on Big Endian machine:
Short bytes 0x7a 0xb7
On the Little Endian machine in gdb:
(gdb) p short_val
$18 = 31415
(gdb) p /x short_val
$19 = 0x7ab7 <- not what I expected.
(gdb) x/2xb &short_val
0xbffff82a: 0xb7 0x7a
(gdb) x/2ub &short_val
0xbffff82a: 183 122
Memory is in the order I would expect but the
print /x shows the order as Big Endian.
Thanks,
J.K.
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
next reply other threads:[~2004-02-05 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 18:00 J K [this message]
2004-02-05 18:04 ` Daniel Jacobowitz
2004-02-06 1:03 ` Andreas Schwab
2004-02-06 1:14 ` Bill Gatliff
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=20040205180043.68640.qmail@web13509.mail.yahoo.com \
--to=ellips@yahoo.com \
--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