From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19144 invoked by alias); 18 Jun 2005 08:51:49 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18981 invoked by uid 22791); 18 Jun 2005 08:51:43 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 18 Jun 2005 08:51:43 +0000 Received: from farnswood.snap.net.nz (p75-tnt1.snap.net.nz [202.124.110.75]) by viper.snap.net.nz (Postfix) with ESMTP id D32DB56311D; Sat, 18 Jun 2005 20:51:40 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 6C65C62A99; Sat, 18 Jun 2005 09:53:33 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17075.57612.684597.392526@farnswood.snap.net.nz> Date: Sat, 18 Jun 2005 08:51:00 -0000 To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] -stack-info-frames In-Reply-To: References: <17075.21529.964955.923197@farnswood.snap.net.nz> <20050617230130.GB21178@nevyn.them.org> <20050617231425.GA22254@nevyn.them.org> <17075.30993.384316.356236@farnswood.snap.net.nz> <20050618015756.GA30430@nevyn.them.org> X-SW-Source: 2005-06/txt/msg00278.txt.bz2 > > Not sure what we could add to the docs. This is what's there: > > If invoked without arguments, this command prints a backtrace for the > > whole stack. If given two integer arguments, it shows the frames whose > > levels are between the two arguments (inclusive). If the two arguments > > are equal, it shows the single frame at the corresponding level. > > Is the actual/new behavior any different, and if so, how? The only behaviour that I've changed is that -stack-selected-frame must have an argument. This now accurately reflects existing documentation. I've talked myself out of implementing -stack-info-frame to give the selected frame because I thought that "-stack-list-frames 0 0" gave this. Now I see that it gives the innermost frame where execution has stopped (the current frame?). I'm not sure that I should have done that because if the user type a CLI command like "up" in the GUD buffer, I don't see how Emacs could keep track of the selected frame. Apple's implementation of GDB/MI presumably has something extra (frame-changed notification?) to do that. Nick