From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] GDB stub changes
Date: Sat, 11 Oct 2008 21:18:33 +0300 [thread overview]
Message-ID: <f43fc5580810111118k13810509m282d7a6943c267d1@mail.gmail.com> (raw)
In-Reply-To: <200810111909.36022.paul@codesourcery.com>
On 10/11/08, Paul Brook <paul@codesourcery.com> wrote:
> I've just committed changes to the qemu gdb remote protocol implementation
> that add support for XML register descriptions. This is a relatively new GDB
> feature that allows qemu to describe what CPU registers are available without
> GDB needing prior knowledge of the CPU. Protocol details can be found in the
> GDB documentation.
>
> Currently only ARM and ColdFire provide these descriptions, and only the basic
> core+fpu registers are described. Future extensions include banked registers,
> privileged registers, MMU state, etc.
>
> Other targets should not see any functional changes. Please test your
> favourite targets and let me know if I broke anything.
make[1]: *** No rule to make target `feature_to_c.sh', needed by
`gdbstub-xml.c'. Stop.
prev parent reply other threads:[~2008-10-11 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 18:09 [Qemu-devel] GDB stub changes Paul Brook
2008-10-11 18:18 ` Blue Swirl [this message]
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=f43fc5580810111118k13810509m282d7a6943c267d1@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).