From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25818 invoked by alias); 23 Apr 2008 08:53:34 -0000 Received: (qmail 25806 invoked by uid 22791); 23 Apr 2008 08:53:32 -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 08:53:07 +0000 Received: from kahikatea.snap.net.nz (135.31.255.123.static.snap.net.nz [123.255.31.135]) by viper.snap.net.nz (Postfix) with ESMTP id 505F13DA363; Wed, 23 Apr 2008 20:52:59 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id C6B378FC6D; Wed, 23 Apr 2008 20:52:53 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18446.63716.779534.2827@kahikatea.snap.net.nz> Date: Wed, 23 Apr 2008 09:50:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] -stack-info-frame/-stack-list-frames In-Reply-To: <200804230933.04964.vladimir@codesourcery.com> References: <18446.45778.889114.789630@kahikatea.snap.net.nz> <18446.49934.972945.419064@kahikatea.snap.net.nz> <200804230933.04964.vladimir@codesourcery.com> 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/msg00504.txt.bz2 > > The frame address is probably of more interest than the pc address, at > > least for frames other than the current one. If the call stack includes > > the frame address for each frame and the watch window gives the variable's > > address then it is possible to infer to which frame that variable belongs. > > What do you mean by "watch window" here, and how the information about frame > a variable belongs to is useful? I mean the window showing a variable's value (represented in Gdb as a variable object). > > In any case, the extra field comes at almost no cost and a frontend can > > choose to ignore it. > > I supposed you don't plan to write documentation that say "these fields are > just in case you need them, feel free to ignore"? Not really because that applies equally to all the other fields, already present, that a front end might not use. > I'm trying to understand > what is *your* intended use of this information, so that I can make up my > mind as to best way to do that. We talked about frame ids before, I think > Dan prefers frame ids, if exposed, to be totally opaque. You appear to > suggest some smart uses of frame addresses, on the other hand, and I don't > understand exactly what uses. I'm just intending to present the frame address to the user to help him understand what he's looking at, not use it as a frame id in any rigorous way. I see that the Totalview debugger presents this information in their call stack (which they call stack trace) window and I think this would be useful, for the reason, I've given too. -- Nick http://www.inet.net.nz/~nickrob