From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-33896-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 12539 invoked by alias); 16 Jun 2004 18:14:43 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 12518 invoked from network); 16 Jun 2004 18:14:43 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 16 Jun 2004 18:14:43 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5GIEfe3002511
	for <gdb-patches@sources.redhat.com>; Wed, 16 Jun 2004 14:14:43 -0400
Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5GIEd020243;
	Wed, 16 Jun 2004 14:14:39 -0400
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 0DB932B9D; Wed, 16 Jun 2004 14:14:21 -0400 (EDT)
Message-ID: <40D08DFC.6030607@gnu.org>
Date: Wed, 16 Jun 2004 18:14:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217
MIME-Version: 1.0
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.
References: <40CEB176.1040904@neurizon.net> <40CF4569.3000404@redhat.com> <40CF972A.1080403@neurizon.net>
In-Reply-To: <40CF972A.1080403@neurizon.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-06/txt/msg00388.txt.bz2

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