From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10435 invoked by alias); 25 Sep 2007 15:57:52 -0000 Received: (qmail 10423 invoked by uid 22791); 25 Sep 2007 15:57:52 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0910.google.com (HELO rv-out-0910.google.com) (209.85.198.187) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Sep 2007 15:57:48 +0000 Received: by rv-out-0910.google.com with SMTP id l15so1564827rvb for ; Tue, 25 Sep 2007 08:57:47 -0700 (PDT) Received: by 10.140.144.4 with SMTP id r4mr431736rvd.1190735867195; Tue, 25 Sep 2007 08:57:47 -0700 (PDT) Received: by 10.140.162.13 with HTTP; Tue, 25 Sep 2007 08:57:47 -0700 (PDT) Message-ID: <6b14b5b00709250857n5e89f833i5058e77cb7cb1534@mail.gmail.com> Date: Tue, 25 Sep 2007 16:03:00 -0000 From: "The Westlakers" To: "The Westlakers" , gdb@sourceware.org Subject: Re: question about GDB message In-Reply-To: <20070925123516.GA1733@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6b14b5b00709242126n5321100m2aad74fd7c7ea58d@mail.gmail.com> <6b14b5b00709242128y54e97509t1c2330a6fc3fa0b@mail.gmail.com> <20070925110500.GA29300@caradoc.them.org> <6b14b5b00709250441v6e04f36bm1553dc901ecb6e17@mail.gmail.com> <20070925114838.GA31304@caradoc.them.org> <6b14b5b00709250527u3df06e1cped38587bf2edd8d@mail.gmail.com> <20070925123516.GA1733@caradoc.them.org> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00204.txt.bz2 On 9/25/07, Daniel Jacobowitz wrote: > On Tue, Sep 25, 2007 at 05:27:13AM -0700, The Westlakers wrote: > > So I did this: > > > > ./configure --target=sparc64-elf, is this right? the resulting GDB > > becomes 32-bit app > > and it can talk to the target in 32-mode, but not 64-bit. > > > > Maybe you could help to make sure I configured it right. > > That's right. It shouldn't matter that the GDB is 32-bit. What goes > wrong talking to a 64-bit target? when GDB issues 'g' packet to the target, the target returns all reg values in 64-bit, but the GDB interprets it as 32-bit, so 'info reg' will not show correct register values. if the target returns in 32-bit values, then info reg can display all values correctly. do not know what is wrong. thanks > > -- > Daniel Jacobowitz > CodeSourcery >