From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25391 invoked by alias); 17 Apr 2006 05:57:05 -0000 Received: (qmail 25383 invoked by uid 22791); 17 Apr 2006 05:57:05 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Apr 2006 05:57:02 +0000 Received: from farnswood.snap.net.nz (p202-124-114-234.snap.net.nz [202.124.114.234]) by viper.snap.net.nz (Postfix) with ESMTP id A245475456D; Mon, 17 Apr 2006 17:56:59 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 500) id 1F10F62A99; Mon, 17 Apr 2006 06:56:53 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17475.11812.479875.969492@farnswood.snap.net.nz> Date: Mon, 17 Apr 2006 06:37:00 -0000 To: Daniel Jacobowitz Cc: Mark Kettenis , gdb@sources.redhat.com Subject: Re: info frame In-Reply-To: <20060417013343.GA4114@nevyn.them.org> References: <17474.53281.404673.189792@farnswood.snap.net.nz> <200604162333.k3GNXLeX004661@elgar.sibelius.xs4all.nl> <17474.58179.83052.362944@farnswood.snap.net.nz> <20060417013343.GA4114@nevyn.them.org> X-Mailer: VM 7.19 under Emacs 22.0.50.36 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00224.txt.bz2 > > >> 553^done,stack=[frame= > > >> {level="0",addr="0x00003db0",fp="0xbffff2c0",...... > > > > 0xbffff2c0 should not be the value of $fp but the value of "frame at..." in > > 'info frame`? > > In fact, it's like that it will be the "frame at" address. But I don't > think it would be wise to architect that into the interface; I think I > explained why earlier, but if not, it's because this is a touchy > internal interface for GDB. If you want to display it to the user, you > might want something different - either explicitly the $sp, or > explictly the architectural $fp register, or explicitly the call frame > address. If you want to use it in a frontend, then all we should offer > is an opaque ID for equality testing, IMHO. > > If GDB changes its internal representation we shouldn't have to update > frontends. I don't think it matters if the internal representation does change, so long as its self consistent. As I mentioned before Totalview displays the fp address of each frame in the call stack. It also displays the appropriate fp address in the window of each watch expression (each expression has its own window). That way, the fp address does act as an ID for the frame and the user can easily see which frame the watch expression belongs to, but its actual value is generally not of interest. -- Nick http://www.inet.net.nz/~nickrob