From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-59309-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 20882 invoked by alias); 17 Oct 2008 10:07:50 -0000
Received: (qmail 20712 invoked by uid 22791); 17 Oct 2008 10:07:49 -0000
X-Spam-Check-By: sourceware.org
Received: from mtaout4.012.net.il (HELO mtaout4.012.net.il) (84.95.2.10)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Oct 2008 10:07:09 +0000
Received: from HOME-C4E4A596F7 ([77.127.24.3]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K8V00AKHO4SJE01@i_mtaout4.012.net.il> for gdb-patches@sourceware.org; Fri, 17 Oct 2008 12:07:41 +0200 (IST)
Date: Fri, 17 Oct 2008 10:07:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [reverse RFC] Add documentation for process record and replay
In-reply-to: <daef60380810162017n15a45d35mee3aea64351b03fc@mail.gmail.com>
X-012-Sender: halo1@inter.net.il
To: teawater <teawater@gmail.com>
Cc: msnyder@vmware.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <uiqrrmt7r.fsf@gnu.org>
References: <daef60380810140800i67753d42jaaf9ef6325756ecd@mail.gmail.com> <daef60380810142250v41c3dcbdk4bff89725d329ea1@mail.gmail.com> <uod1mnx1z.fsf@gnu.org> <48F63B15.3070705@vmware.com> <uej2hod8w.fsf@gnu.org> <daef60380810151909t9382697u5e78b1d90097270@mail.gmail.com> <ubpxlnhut.fsf@gnu.org> <daef60380810160004x173b02adh11eaca2f59a0166e@mail.gmail.com> <daef60380810160035we364816k91a4d3fbc06b46dc@mail.gmail.com> <uy70omli6.fsf@gnu.org> <daef60380810162017n15a45d35mee3aea64351b03fc@mail.gmail.com>
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: 2008-10/txt/msg00425.txt.bz2

> Date: Fri, 17 Oct 2008 11:17:59 +0800
> From: teawater <teawater@gmail.com>
> Cc: msnyder@vmware.com, gdb-patches@sourceware.org
> 
> Thanks Eli.
> I make a new one.

Almost there ;-)

> > I'm somewhat concerned about the fact that the functionality and
> > limitations of the ``record and replay'' target are not described at
> > all.  If I were to debug using such an architecture, I'd like to know
> > what it can and cannot do.  For example, if I replay, does the I/O
> > happen like it happened during the recorded session?  What about
> > signals? crashes? etc.  Are there things that simply cannot be
> > reproduced exactly, due to fundamental limitations of the replay
> > target?

Do you have an opinion about these concerns?

> +Stop process record and replay target at once. When Process record and
                                                ^^
Still one space.

> +earlier point), the inferior process will become ``live" at that earlier state,

``live'', not ``live".  (There are more cases of this in the text.)