Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Steven Johnson <sjohnson@neurizon.net>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Small problem with Remote Protocol register fetching.
Date: Wed, 16 Jun 2004 18:14:00 -0000	[thread overview]
Message-ID: <40D08DFC.6030607@gnu.org> (raw)
In-Reply-To: <40CF972A.1080403@neurizon.net>

Hmm, you should be wanting to change your remote target :-) :-)

By doing that you ensure that the remote-target interoperates with any 
released GDBs.  If you don't you ensure that at best your target 
operates with only a not-yet-released mainline GDB.

As for remote.c and the protocol, yes need to think of something.  My 
opinion is that, regardless, we need to change the spec to ``lower-case 
@sc{hex}'' - to ensure that compatibility.

Andrew



  reply	other threads:[~2004-06-16 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15  8:21 Steven Johnson
2004-06-15 15:26 ` Andrew Cagney
2004-06-15 18:52 ` Michael Snyder
2004-06-16  0:41   ` Steven Johnson
2004-06-16 18:14     ` Andrew Cagney [this message]
2004-06-16 22:47       ` Steven Johnson
2004-06-24 18:12         ` Andrew Cagney

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=40D08DFC.6030607@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    --cc=sjohnson@neurizon.net \
    /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