From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13805 invoked by alias); 6 May 2005 20:59:32 -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 13673 invoked from network); 6 May 2005 20:59:27 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 6 May 2005 20:59:27 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DU9uw-0004q1-Tc; Fri, 06 May 2005 16:59:27 -0400 Date: Fri, 06 May 2005 20:59:00 -0000 From: Daniel Jacobowitz To: "Decker, Paul" Cc: gdb@sourceware.org Subject: Re: Available registers as a target property Message-ID: <20050506205926.GA18527@nevyn.them.org> Mail-Followup-To: "Decker, Paul" , gdb@sourceware.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00077.txt.bz2 On Fri, May 06, 2005 at 01:55:12PM -0400, Decker, Paul wrote: > > > I posed a similar question to the group about a week ago. We have > target variants which may or may not support a particular register set. > My question involved gdb being able to query the target to determine the > register set, and this sounds like a workable approach, in fact, our > target is already setup to do this, all it needs is to be 'asked' to > return the registers in the set, and a description of the registers, so > naturally, I think this would be a great addition. Does this way of describing registers offer enough flexibility for your target? -- Daniel Jacobowitz CodeSourcery, LLC