From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31286 invoked by alias); 22 Nov 2008 00:48:36 -0000 Received: (qmail 31238 invoked by uid 22791); 22 Nov 2008 00:48:36 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Nov 2008 00:48:00 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id A96D8C013; Fri, 21 Nov 2008 16:47:59 -0800 (PST) Received: from [10.20.92.151] (promb-2s-dhcp151.eng.vmware.com [10.20.92.151]) by mailhost4.vmware.com (Postfix) with ESMTP id 9BEB0C9A8E; Fri, 21 Nov 2008 16:47:59 -0800 (PST) Message-ID: <492756B3.6080809@vmware.com> Date: Sat, 22 Nov 2008 00:48:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Joel Brobecker CC: Paul Pluzhnikov , Gaius Mulley , Sandeep222 , "gdb@sourceware.org" Subject: Re: How to store function-name and its return values while program runs References: <20618721.post@talk.nabble.com> <87skpl1gy7.fsf@j228-gm.comp.glam.ac.uk> <4927062C.4020806@vmware.com> <8ac60eac0811211410s2196e9a1g28c824850b222bf6@mail.gmail.com> <20081121222835.GA16751@adacore.com> In-Reply-To: <20081121222835.GA16751@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00140.txt.bz2 Joel Brobecker wrote: >> I wished many times that above worked, but it doesn't: 'finish' >> appears to interrupt flow of script, and subsequent commands are >> never executed: > [...] >> Is this a bug? > > It actually isn't. The manual tries to explain why: > >> Any other commands in the command list, after a command that resumes >> execution, are ignored. This is because any time you resume execution >> (even with a simple next or step), you may encounter another >> breakpoint--which could have its own command list, leading to >> ambiguities about which list to execute. > > Most of the users at AdaCore view this as a limitation, but I haven't > really had the energy to look at improving this. Mumble. I'm sorry -- of course I knew about that, but I must have dreamed that somebody had done something about it a while back...