From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] GDB stub changes
Date: Sat, 11 Oct 2008 19:09:35 +0100 [thread overview]
Message-ID: <200810111909.36022.paul@codesourcery.com> (raw)
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.
Paul
next reply other threads:[~2008-10-11 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 18:09 Paul Brook [this message]
2008-10-11 18:18 ` [Qemu-devel] GDB stub changes Blue Swirl
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=200810111909.36022.paul@codesourcery.com \
--to=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).