From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1855 invoked by alias); 8 Jun 2005 22:59:02 -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 1713 invoked by uid 22791); 8 Jun 2005 22:58:38 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 08 Jun 2005 22:58:38 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1Dg9VL-0004EM-Fa; Wed, 08 Jun 2005 18:58:35 -0400 Date: Wed, 08 Jun 2005 22:59:00 -0000 From: Daniel Jacobowitz To: Shaun Jackman Cc: gdb@sources.redhat.com Subject: Re: ARM register pages Message-ID: <20050608225835.GA16214@nevyn.them.org> Mail-Followup-To: Shaun Jackman , gdb@sources.redhat.com References: <7f45d93905060815004a8a9b2d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f45d93905060815004a8a9b2d@mail.gmail.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00075.txt.bz2 On Wed, Jun 08, 2005 at 03:00:46PM -0700, Shaun Jackman wrote: > Is there an "info registers" command that displays the paged registers > for each ARM mode, such as $lr_svc and $lr_abt? GDB doesn't recognize > these names on the command line for printing/setting. Could this be a > wishlist item? GDB doesn't even know that these registers exist, yet. The normal ARM remote protocol doesn't transfer them, either. > A "data abort" ARM exception sets the $cpsr to 0x17, the program > counter to 0x10, and the $lr_abt to the previous value of the program > counter. The backtrace command doesn't work now because (I'm guessing) > GDB sees $lr_abt and $sp_abt instead of the $lr_usr and $sp_usr that > contain the useful backtrace information. How can I get a useful > backtrace after a data abort exception? GDB doesn't want to do this by default, usually, because they are likely to be in different executable images. If they aren't, assuming that your abort handler saves the banked lr to the stack, you can write DWARF-2 information to describe where it lives. -- Daniel Jacobowitz CodeSourcery, LLC