From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1613 invoked by alias); 11 Jul 2005 15:49:31 -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 1598 invoked by uid 22791); 11 Jul 2005 15:49:28 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 15:49:28 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1Ds0X8-000892-Og; Mon, 11 Jul 2005 11:49:26 -0400 Date: Mon, 11 Jul 2005 15:49:00 -0000 From: Daniel Jacobowitz To: Andrew STUBBS Cc: GDB Subject: Re: Invalid registers Message-ID: <20050711154926.GB30937@nevyn.them.org> Mail-Followup-To: Andrew STUBBS , GDB 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-07/txt/msg00118.txt.bz2 On Mon, Jul 11, 2005 at 04:39:51PM +0100, Andrew STUBBS wrote: > Hi, > > I have been having a little trouble updating from GDB 5.3 to GDB 6.3. > > It used to be the case that GDB would report '*value not available*' (for > SH - I haven't checked other architectures) if the value of a register is > not known in the current stack frame. However, it no longer does this. > Since I assume it has not acquired some way to find out what that value > was, I also assume this is somehow broken. How's it supposed to know that the value is not available? If you want to do this based on the standard call ABI, please take a look at the current callers of dwarf2_frame_set_init_reg. -- Daniel Jacobowitz CodeSourcery, LLC