This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: ARM: where are special registers?
- From: Dmitry Smirnov <divis1969 at mail dot ru>
- To: gdb at sourceware dot org
- Date: Tue, 08 Jul 2008 17:38:55 +0400
- Subject: Re: ARM: where are special registers?
- References: <20080708120801.GA28333@caradoc.them.org>
- Reply-to: Dmitry Smirnov <divis1969 at mail dot ru>
I've found in ch.11.1 at http://sourceware.org/gdb/current/onlinedocs/gdbint_11.html#SEC89 :
<quote>
A description may come from a user specified file (XML), the remote `qXfer:features:read' packet (also XML), or from any custom to_read_description routine in the target vector. For instance, the remote target supports guessing whether a MIPS target is 32-bit or 64-bit based on the size of the `g' packet.
<quote/>
Is there any example of this XML?
What remote stub shall respond to "qXfer:features:read"? Just this XML content?
Am I right that before GDB asks for "qXfer:features:read", I shall implement "qSupported" handling in a stub with this "qXfer:features:read" as a response?
-----Original Message-----
From: Daniel Jacobowitz <drow@false.org>
To: Dmitry Smirnov <divis1969@mail.ru>
Date: Tue, 8 Jul 2008 08:08:01 -0400
Subject: Re: ARM: where are special registers?
>
> On Tue, Jul 08, 2008 at 01:07:51PM +0400, Dmitry Smirnov wrote:
> > Hi,
> >
> > As you know, ARM processor have some special registers like CPSR, SPSR_svc, r8_usr, etc.
> > While running GDB I cannot see these registers (CPSR only).
> > My GDB is connected to remote ARM simulator, so maybe the simulator is the problem area?
>
> Please see the manual chapter on Target Descriptions - that describes
> how to report additional registers.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>