From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1050 invoked by alias); 8 Jun 2005 22:01:01 -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 32417 invoked by uid 22791); 8 Jun 2005 22:00:48 -0000 Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.200) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 08 Jun 2005 22:00:48 +0000 Received: by rproxy.gmail.com with SMTP id a36so245565rnf for ; Wed, 08 Jun 2005 15:00:46 -0700 (PDT) Received: by 10.11.116.19 with SMTP id o19mr105012cwc; Wed, 08 Jun 2005 15:00:46 -0700 (PDT) Received: by 10.11.99.15 with HTTP; Wed, 8 Jun 2005 15:00:46 -0700 (PDT) Message-ID: <7f45d93905060815004a8a9b2d@mail.gmail.com> Date: Wed, 08 Jun 2005 22:01:00 -0000 From: Shaun Jackman Reply-To: Shaun Jackman To: gdb@sources.redhat.com Subject: ARM register pages Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-SW-Source: 2005-06/txt/msg00074.txt.bz2 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? 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? Thanks, Shaun GDB 6.2.1