From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-66390-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 18347 invoked by alias); 31 Aug 2009 17:54:42 -0000
Received: (qmail 18336 invoked by uid 22791); 31 Aug 2009 17:54:42 -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; Mon, 31 Aug 2009 17:54:35 +0000
Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) 	by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 18F2F5500C; 	Mon, 31 Aug 2009 10:54:34 -0700 (PDT)
Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) 	by jupiter.vmware.com (Postfix) with ESMTP id 0C4D0DC119; 	Mon, 31 Aug 2009 10:54:34 -0700 (PDT)
Message-ID: <4A9C0E58.6080500@vmware.com>
Date: Mon, 31 Aug 2009 17:56:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20080411)
MIME-Version: 1.0
To: Jakob Engblom <jakob@virtutech.com>
CC: 'Eli Zaretskii' <eliz@gnu.org>,   "glaw@undo-software.com" <glaw@undo-software.com>,  "gdb-patches@sourceware.org" <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> <4A9865A5.1020703@vmware.com> <00d201ca2a33$454aa920$cfdffb60$@com>
In-Reply-To: <00d201ca2a33$454aa920$cfdffb60$@com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-08/txt/msg00589.txt.bz2

Jakob Engblom wrote:
>>   * the end (beginning) of a replay log if one is being used.
> 
> Subtle question here: does this mean that process record STOPS if you reach the
> point in time where its recording ends? Or does it just start to extend the
> recorded execution?

It stops.  Extending the recording might be a future enhancement.

> I.e., in process record, do you have to record everything first and then debug
> it? 

You can record everything first and then debug it.
You can also debug it while you're recording it.
I *think* (and this is just based on my experience,
Hui may be able to say something different) that the
recording mode is "over" as soon as you go into
replay mode, and so that represents the "end" of
your recording.