From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27204 invoked by alias); 28 Aug 2009 23:17:39 -0000 Received: (qmail 27193 invoked by uid 22791); 28 Aug 2009 23:17:38 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 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.43rc1) with ESMTP; Fri, 28 Aug 2009 23:17:33 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id A148313504; Fri, 28 Aug 2009 16:17:28 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost4.vmware.com (Postfix) with ESMTP id 9571AC9A2A; Fri, 28 Aug 2009 16:17:28 -0700 (PDT) Message-ID: <4A9865A5.1020703@vmware.com> Date: Fri, 28 Aug 2009 23:28:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Eli Zaretskii CC: "glaw@undo-software.com" , "jakob@virtutech.com" , "gdb-patches@sourceware.org" Subject: Re: GDB MI Reverse Commands added [2 of 3] References: <00cf01ca265a$d4110dc0$7c332940$@com> <83tyzucw8p.fsf@gnu.org> <002b01ca27c7$1316d8c0$39448a40$@com> <833a7ccj52.fsf@gnu.org> <4A97BA98.4010105@undo-software.com> <83y6p4aweu.fsf@gnu.org> <4A980D06.40002@undo-software.com> <83ljl3c16f.fsf@gnu.org> <4A981551.4060504@vmware.com> <83k50nbrja.fsf@gnu.org> In-Reply-To: <83k50nbrja.fsf@gnu.org> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-08/txt/msg00527.txt.bz2 Eli Zaretskii wrote: >> Date: Fri, 28 Aug 2009 10:35:13 -0700 >> From: Michael Snyder >> CC: Greg Law , >> "jakob@virtutech.com" , >> "gdb-patches@sourceware.org" >> >> I think we should mention that "running off the end of the log" is >> one way in which a reverse continue may terminate, because in fact >> that is something that may happen in all of the current implementations. > > Please suggest a wording, and if it's clear, I won't mind. How about this? (please add markups) Resumes the execution of the inferior program, which will continue to execute until it reaches a debugger stop event. If the @samp{--reverse} option is specified, execution resumes in reverse until it reaches a stop event. Stop events may include * breakpoints or watchpoints * signals or exceptions) * the end of the process (or its beginning if --reverse) * the end (beginning) of a replay log if one is being used.