From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14165 invoked by alias); 21 Nov 2002 09:44:25 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 14151 invoked from network); 21 Nov 2002 09:44:21 -0000 Received: from unknown (HELO dublin.ACT-Europe.FR) (212.157.227.154) by sources.redhat.com with SMTP; 21 Nov 2002 09:44:21 -0000 Received: from torino.act-europe.fr (torino.int.act-europe.fr [10.10.0.130]) by dublin.ACT-Europe.FR (Postfix) with ESMTP id 3E079229FF9; Thu, 21 Nov 2002 10:44:20 +0100 (MET) Received: by torino.act-europe.fr (Postfix, from userid 500) id C84D7F404; Thu, 21 Nov 2002 14:44:19 +0500 (GMT-5) Date: Thu, 21 Nov 2002 01:44:00 -0000 From: Romain Berrendonner To: Kevin Buettner Cc: gdb@sources.redhat.com Subject: Re: compatibility between gdb and stub Message-ID: <20021121094419.GB8709@torino.act-europe.fr> References: <20021118140945.GF1252@torino.act-europe.fr> <1021118225613.ZM5538@localhost.localdomain> <20021119092051.GD1217@torino.act-europe.fr> <1021120210450.ZM24337@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1021120210450.ZM24337@localhost.localdomain> User-Agent: Mutt/1.4i X-SW-Source: 2002-11/txt/msg00311.txt.bz2 On 2002-11-20, Kevin Buettner wrote : > > As I understand it, if a stub replies with a short "g" packet, then > gdb will simply regard the missing registers as being unavailable. > Let's take the example of the 750, with a stub not aware of fpscr. They are many registers after fpscr (the first of them is sr0). With this scheme, when the stub sends back the answer to a 'g' packet, gdb will consider that the content of fpscr is the content of sr0, and that thrm3 (the last register) is not available. This is clumsy, but the 'qRegisters' packet should improve this behaviour :-) -- Romain