From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10688 invoked by alias); 22 Apr 2003 17:06:45 -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 10681 invoked from network); 22 Apr 2003 17:06:44 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 22 Apr 2003 17:06:44 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id BE6572B2F; Tue, 22 Apr 2003 13:06:42 -0400 (EDT) Message-ID: <3EA576A2.9060106@redhat.com> Date: Tue, 22 Apr 2003 17:06:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jan Hoogerbrugge Cc: gdb@sources.redhat.com Subject: Re: Endianness and remote debugging References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00248.txt.bz2 > The problem has been solved after that I discovered that register values are sent in target order while other values are sent in big endian order. > > BWT, I was refering to the 'qPmodethreadid' query of section D.4. Ah, yes, that ID is in network byte order. Andrew