From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17720 invoked by alias); 2 Dec 2001 23:02:42 -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 17683 invoked from network); 2 Dec 2001 23:02:42 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by hostedprojects.ges.redhat.com with SMTP; 2 Dec 2001 23:02:42 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16AfdY-00025k-00 for ; Sun, 02 Dec 2001 18:03:04 -0500 Date: Sun, 02 Dec 2001 15:02:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: The REG_NUM and REGISTER_BYTES problem Message-ID: <20011202180304.A7998@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <3C084D16.4090205@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C084D16.4090205@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00003.txt.bz2 On Fri, Nov 30, 2001 at 10:23:02PM -0500, Andrew Cagney wrote: > To address this, I intend changing regcache and remote.c so that they > treat all registers equal (don't differentiate between real and psuedo > registers). Instead, regchace reserves space for all of them, and > remote.c will fetch any of them when so asked. Exactly what to do with > all that potential regcache space being the responsibility of the target > architecture. > > By doing this, the immdiate restriction of not being able to expand the > number of registers is lifted. While some of REGISTER_BYTES and > NUM_REGS special effects will remain, they won't be causing GDB's > ability to handle large register sets. > > Thoughts? Well, how will this affect pseudo registers that we can provide but that the remote stub can not? I'm pretty sure there are some. Is the intent that such registers "should not" be fetched? On the subject of the remote protocol, both you and I posted scripts to generate a register packet description from a text file. What're your thoughts on adding one of those? -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer