From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30187 invoked by alias); 3 Dec 2004 01:29:07 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30174 invoked from network); 3 Dec 2004 01:29:04 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by sourceware.org with SMTP; 3 Dec 2004 01:29:04 -0000 Received: from [10.0.1.2] (h000393256f12.ne.client2.attbi.com[24.61.199.96]) by comcast.net (sccrmhc12) with SMTP id <2004120301290301200bullke>; Fri, 3 Dec 2004 01:29:03 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Fri, 03 Dec 2004 01:29:00 -0000 Subject: Re: RFA: Recognize 'x' in response to 'p' packet From: Paul Schlie To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2004-12/txt/msg00055.txt.bz2 > Jim Blandy > * remote.c (fetch_register_using_p): Recognize 'x's for the value > of the register as indicating that the register's value is not > available. Out of curiosity, under what practical circumstances would the value of a register not be accessible? (and if not, shouldn't an error be returned, as opposed to an 'x' which is converted to a 0 anyway? Which I've noticed "g" packets also assume?)