Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Brendan Kehoe <brendan@zen.org>
Cc: gdb@sourceware.org
Subject: Re: support for multiple ARM register banks in GDB
Date: Thu, 11 May 2006 15:00:00 -0000	[thread overview]
Message-ID: <20060511145349.GA6923@nevyn.them.org> (raw)
In-Reply-To: <44634F3D.1050401@zen.org>

On Thu, May 11, 2006 at 03:50:37PM +0100, Brendan Kehoe wrote:
> Hi folks,
> 
> Is anyone already looking at GDB's port to the ARM, and in particular
> what it believes is the single register bank on the chip?  For
> processors like the ARM7TDMI, there are a few register banks depending
> on the current mode of the ARM.  In order to debug (not C++) exceptions
> on an ARM embedded target, it's necessary to be able to look at a
> specific bank's register like r13_irq.  This sort of stuff appears to be
> in place in the simulator, but not in GDB itself.

I've implemented banked register support, as a sample application of
the XML-based register description work I've posted about several
times.  The GDB client and the RDI-based GDB stub we ship in
the 2006-Q1 CodeSourcery release includes support for banked registers.
Of course, if your target isn't RDI-based, that doesn't directly help
you.  But it shouldn't be hard to do for a custom debug stub either.

(It took all of an hour or two once the XML bits were in place, so I'd
say it was a successful test run).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-11 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 14:59 Brendan Kehoe
2006-05-11 15:00 ` Daniel Jacobowitz [this message]
2006-05-13 14:18 ` Mark Kettenis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060511145349.GA6923@nevyn.them.org \
    --to=drow@false.org \
    --cc=brendan@zen.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox