Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: J K <ellips@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb print /x always big endian order?
Date: Fri, 06 Feb 2004 01:03:00 -0000	[thread overview]
Message-ID: <jeu1259fyx.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040205180043.68640.qmail@web13509.mail.yahoo.com> (J. K.'s message of "Thu, 5 Feb 2004 10:00:42 -0800 (PST)")

J K <ellips@yahoo.com> writes:

>  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.

The print command just prints a value, and values don't have endianess.
Only memory contents have.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2004-02-06  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 18:00 J K
2004-02-05 18:04 ` Daniel Jacobowitz
2004-02-06  1:03 ` Andreas Schwab [this message]
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=jeu1259fyx.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=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