From: Daniel Jacobowitz <drow@false.org>
To: s88 <dave.tw@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: info registers
Date: Thu, 06 Dec 2007 13:57:00 -0000 [thread overview]
Message-ID: <20071206135742.GA27856@caradoc.them.org> (raw)
In-Reply-To: <c9d32f760712060012m6d10d60do4d09fcfa62c09f31@mail.gmail.com>
On Thu, Dec 06, 2007 at 04:12:26PM +0800, s88 wrote:
> Hi all:
> I'm modifying gdb v6.06 for our ARM simulator as a remote target.
> Someone want to watch additional register information, such as system
> mode registers...
>
> which file should I modify?
> I know to modify the protocol is necessary!!
Not any more, it isn't. Please use the latest release and look at the
Target Descriptions section of the manual.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-12-06 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 8:12 s88
2007-12-06 13:57 ` Daniel Jacobowitz [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=20071206135742.GA27856@caradoc.them.org \
--to=drow@false.org \
--cc=dave.tw@gmail.com \
--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