From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30478 invoked by alias); 9 Jun 2005 17:04:04 -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 30446 invoked by uid 22791); 9 Jun 2005 17:03:56 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 09 Jun 2005 17:03:56 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DgQRe-00027i-0o; Thu, 09 Jun 2005 13:03:54 -0400 Date: Thu, 09 Jun 2005 17:04:00 -0000 From: Daniel Jacobowitz To: Shaun Jackman Cc: gdb@sources.redhat.com Subject: Re: ARM register pages Message-ID: <20050609170353.GA8119@nevyn.them.org> Mail-Followup-To: Shaun Jackman , gdb@sources.redhat.com References: <7f45d93905060815004a8a9b2d@mail.gmail.com> <20050608225835.GA16214@nevyn.them.org> <7f45d93905060909461870392b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f45d93905060909461870392b@mail.gmail.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00080.txt.bz2 On Thu, Jun 09, 2005 at 09:46:32AM -0700, Shaun Jackman wrote: > On 6/8/05, Daniel Jacobowitz wrote: > > 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. > > By the "normal ARM remote protocol" do you mean RDP/RDI, or the GDB > remote protocol for ARM? Does the latter know about these registers? The latter. RDI does, of course. > > 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. > > My data abort handler currently looks like: > abt: b abt > When everything freezes I interrupt the debugger to look at what's > happened. I'd like to get a backtrace of the user mode from this > state. The easiest solution will be to do this instead: abt: [copy the banked address to lr, which is not useful at this point] 1: b 1b -- Daniel Jacobowitz CodeSourcery, LLC