From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5289 invoked by alias); 6 Feb 2004 01:14:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5282 invoked from network); 6 Feb 2004 01:14:06 -0000 Received: from unknown (HELO saturn.billgatliff.com) (209.251.101.200) by sources.redhat.com with SMTP; 6 Feb 2004 01:14:06 -0000 Received: by saturn.billgatliff.com (Postfix, from userid 500) id EA54D4E0004; Thu, 5 Feb 2004 19:14:05 -0600 (CST) References: <20040205180043.68640.qmail@web13509.mail.yahoo.com> In-Reply-To: From: "Bill Gatliff" To: gdb@sources.redhat.com Subject: Re: gdb print /x always big endian order? Date: Fri, 06 Feb 2004 01:14:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <20040206011405.EA54D4E0004@saturn.billgatliff.com> X-SW-Source: 2004-02/txt/msg00053.txt.bz2 JK: Indeed. If you want to see endianness, use 'x' instead, and ask it for a string of hex bytes. :^) b.g. Andreas Schwab writes: > J K 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." -- Bill Gatliff Embedded GNU, Linux training and development. bgat@billgatliff.com