From: Dmitry Smirnov <divis1969@mail.ru>
To: gdb@sourceware.org
Subject: Re: ARM: where are special registers?
Date: Tue, 08 Jul 2008 13:39:00 -0000 [thread overview]
Message-ID: <E1KGDPD-0001fs-00.divis1969-mail-ru@f127.mail.ru> (raw)
In-Reply-To: <20080708120801.GA28333@caradoc.them.org>
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
>
next prev parent reply other threads:[~2008-07-08 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 9:08 Dmitry Smirnov
2008-07-08 12:08 ` Daniel Jacobowitz
2008-07-08 13:39 ` Dmitry Smirnov [this message]
2008-07-08 22:33 ` Daniel Jacobowitz
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=E1KGDPD-0001fs-00.divis1969-mail-ru@f127.mail.ru \
--to=divis1969@mail.ru \
--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