From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18898 invoked by alias); 23 Apr 2008 22:15:52 -0000 Received: (qmail 18889 invoked by uid 22791); 23 Apr 2008 22:15:52 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Apr 2008 22:15:17 +0000 Received: from kahikatea.snap.net.nz (190.30.255.123.static.snap.net.nz [123.255.30.190]) by viper.snap.net.nz (Postfix) with ESMTP id 084FD3D9F97; Thu, 24 Apr 2008 10:15:15 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id B0DD18FC6E; Thu, 24 Apr 2008 10:15:08 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18447.46315.956290.915310@kahikatea.snap.net.nz> Date: Wed, 23 Apr 2008 23:04:00 -0000 To: Daniel Jacobowitz Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] -stack-info-frame/-stack-list-frames In-Reply-To: <20080423125410.GA19773@caradoc.them.org> References: <18446.45778.889114.789630@kahikatea.snap.net.nz> <200804230933.04964.vladimir@codesourcery.com> <18446.63716.779534.2827@kahikatea.snap.net.nz> <200804231349.35190.vladimir@codesourcery.com> <18447.12269.389044.431822@kahikatea.snap.net.nz> <20080423125410.GA19773@caradoc.them.org> X-Mailer: VM 7.19 under Emacs 22.2.50.2 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00537.txt.bz2 > My concern about this has been, and still is, that front ends will > assign more meaning to it than it really has. This is one of the > trickiest parts of GDB. We already use frame addresses (specifically > $fp) to create varobjs in non-current frames; this is basically the > only thing the entire complicated frame_base machinery is used for > when not using stabs and it really should go away. I thought there was sometimes an eight byte offset as Mark Kettenis so eloquently described in: http://sourceware.org/ml/gdb/2006-04/msg00218.html But thats a good cas in point. If the frontend end is to operate in a stateless manner, as Vladimir has suggested, and varobjs are created in non-selected frames, it needs to know the frame addresses: -var-create - FRAME-ADDR EXPRESSION > How about we call it the stack address of the frame instead of the > frame address? Then it can come from the unwound $sp, which will > be at the other end of the frame and is better defined. I don't care what it's called. If value this is different from get_frame_base (fi) how is it computed? -- Nick http://www.inet.net.nz/~nickrob