From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4536 invoked by alias); 22 May 2007 15:34:29 -0000 Received: (qmail 4518 invoked by uid 22791); 22 May 2007 15:34:26 -0000 X-Spam-Check-By: sourceware.org Received: from return.false.org (HELO return.false.org) (66.207.162.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 May 2007 15:34:21 +0000 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id 7A7484B26D; Tue, 22 May 2007 10:34:19 -0500 (CDT) Received: from caradoc.them.org (dsl093-172-095.pit1.dsl.speakeasy.net [66.93.172.95]) by return.false.org (Postfix) with ESMTP id 4DB3E4B262; Tue, 22 May 2007 10:34:15 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1HqWNK-00063i-J8; Tue, 22 May 2007 11:34:14 -0400 Date: Tue, 22 May 2007 15:34:00 -0000 From: Daniel Jacobowitz To: Robert Norton Cc: gdb@sourceware.org Subject: Re: Info reg sp Message-ID: <20070522153414.GA23001@caradoc.them.org> Mail-Followup-To: Robert Norton , 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.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00107.txt.bz2 On Tue, May 22, 2007 at 08:24:34AM -0700, Robert Norton wrote: > The problem is that frame_map_name_to_regnum returns a value greater > than NUM_REGS+NUM_PSEUDO_REGS because there is a builtin user reg by > that name which is returned by user_reg_map_name_to_regnum. The question > is: should my print_registers_info be able to handle this (if so how? I > suppose by calling value_of_user_reg) or is this code broken? Hmm, good question. I could make an argument either way. Every port has this same problem, but then again only the default print_registers_info and those with their own print_registers_info would have to be fixed. Still, it's nasty that value_of_register can handle user registers but nothing else can. Maybe frame.c should also? I've been starting to use user registers more heavily lately, since pseudo registers have strange problems - they only come from a regcache, not from a frame. -- Daniel Jacobowitz CodeSourcery