From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32161 invoked by alias); 17 Apr 2006 00:37:32 -0000 Received: (qmail 32151 invoked by uid 22791); 17 Apr 2006 00:37:32 -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 00:37:28 +0000 Received: from farnswood.snap.net.nz (p202-124-114-126.snap.net.nz [202.124.114.126]) by viper.snap.net.nz (Postfix) with ESMTP id EBAED754645; Mon, 17 Apr 2006 12:37:25 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 500) id AF01062A99; Mon, 17 Apr 2006 01:37:23 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17474.58179.83052.362944@farnswood.snap.net.nz> Date: Mon, 17 Apr 2006 05:54:00 -0000 To: Mark Kettenis Cc: gdb@sources.redhat.com Subject: Re: info frame In-Reply-To: <200604162333.k3GNXLeX004661@elgar.sibelius.xs4all.nl> References: <17474.53281.404673.189792@farnswood.snap.net.nz> <200604162333.k3GNXLeX004661@elgar.sibelius.xs4all.nl> 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/msg00221.txt.bz2 ... > Note that while %ebp is usually used as a frame pointer register, the > architecture doesn't actually force you to do that. Nowadays > compilers can and will generate frameless functions, and for those, > the value %ebp is meaningless. Thanks for the explanation. Does this mean that if we choose to print the frame address in MI as part of the output of -stack-list-frames: >> Can somebody suggest the right fix? So far, I think that the simplest >> approach is to make gdb print stack address of current frame, like >> is done >> on the Apple branch: >> >> 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`? -- Nick http://www.inet.net.nz/~nickrob