From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-37594-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 8095 invoked by alias); 23 Dec 2004 17:12:25 -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 8061 invoked from network); 23 Dec 2004 17:12:19 -0000
Received: from unknown (HELO nevyn.them.org) (66.93.172.17)
  by sourceware.org with SMTP; 23 Dec 2004 17:12:19 -0000
Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian))
	id 1ChWVa-0003p5-Oq
	for <gdb-patches@sources.redhat.com>; Thu, 23 Dec 2004 12:12:14 -0500
Date: Thu, 23 Dec 2004 17:22:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: Recognize 'x' in response to 'p' packet
Message-ID: <20041223171214.GA14604@nevyn.them.org>
Mail-Followup-To: gdb-patches@sources.redhat.com
References: <vt2mzww8c2z.fsf@zenia.home> <vt2wtvilzhb.fsf@zenia.home> <20041217193240.GA19185@nevyn.them.org> <vt2oegslfis.fsf@zenia.home> <20041217224540.GA1084@nevyn.them.org> <vt2mzw7jqbh.fsf@zenia.home> <vt2ekhhhtgw.fsf@zenia.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <vt2ekhhhtgw.fsf@zenia.home>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-SW-Source: 2004-12/txt/msg00429.txt.bz2

On Thu, Dec 23, 2004 at 11:25:51AM -0500, Jim Blandy wrote:
> Jim Blandy <jimb@redhat.com> writes:
> 
> > Daniel Jacobowitz <drow@false.org> writes:
> > > My real question, though, is what you needed this for - and whether
> > > marking the register unavailable fixes it.
> > 
> > The Red Hat Debug Agent generates replies to 'p' packets that contain
> > 'x's.  GDB generally seems to work, but 'info thread' fares poorly.
> > Simply parsing the response at all should fix the problem; I'll make
> > sure that marking the register as unavailable doesn't cause any new
> > problems.
> > 
> > Thanks for the review!
> 
> Okay, here's the revised patch, against the properly re-indented
> sources.  Tested against RDA.
> 
> 2004-12-17  Jim Blandy  <jimb@redhat.com>
> 
> 	* remote.c (fetch_register_using_p): Recognize a register value
> 	starting with 'x' as indicating an unfetchable register.

OK, thanks!  I will be getting around to adding 'p' to gdbserver soon,
so I'll need this too.

-- 
Daniel Jacobowitz