From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5858 invoked by alias); 18 Jun 2005 23:20:41 -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 5796 invoked by uid 22791); 18 Jun 2005 23:20:35 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 18 Jun 2005 23:20:35 +0000 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1Djmc4-0007Rg-Un; Sat, 18 Jun 2005 19:20:33 -0400 Date: Sat, 18 Jun 2005 23:20:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Eli Zaretskii , gdb-patches@sources.redhat.com Subject: Re: [PATCH] -stack-info-frames Message-ID: <20050618232032.GA28368@nevyn.them.org> Mail-Followup-To: Nick Roberts , Eli Zaretskii , gdb-patches@sources.redhat.com 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> <17075.57612.684597.392526@farnswood.snap.net.nz> <20050618155742.GB3663@nevyn.them.org> <17076.42233.730605.834264@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17076.42233.730605.834264@farnswood.snap.net.nz> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00290.txt.bz2 On Sun, Jun 19, 2005 at 10:49:29AM +1200, Nick Roberts wrote: > This is what used to happen (I get this with GNU gdb 5.2.1-2mdk, for example) > But now with GDB in CVS, I get the same output as with > "-interpreter-exec console up" (apart from "up\n" in the log stream) i.e. > > up > &"up\n" > ~"#1 0x08048641 in main (argc=1, argv=0xbffff794) at myprog.c:81\n" > ~"81\t myprint (i,a[i] /* hello */);\n" > ^done > > I don't know why you don't also get this. I do now. It didn't even occur to me that this would change between 6.3 and CVS. I'll assume that was a deliberate change... is this going to bust frontends? > Before I looked at the code, I presumed that GDB detected when execution had > stopped and the printed out "*stopped" (in which case this would happen also > with CLI commands). Looking at it, I see it is printed in > mi_execute_async_cli_command so that it appears as command output rather than > event notification > > > Meanwhile, we don't have this ability. So maybe we do need > > -stack-info-frame, without an argument. > > Yes, unless Apple's proposed merge will provide the necessary information. Let's not wait on that. You've demonstrated a use for -stack-info-frame relative to the current source base. That's plenty good enough for me. Of course now we need to re-add the documentation (with example this time). A test case would be nice too. Since we've decided that we do want this feature, could you put that together? I'm going to be travelling all next week, but I should have time to review the occasional patch anyway. -- Daniel Jacobowitz CodeSourcery, LLC