Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: msnyder@vmware.com, gdb-patches@sourceware.org
Subject: Re: [reverse RFC] Add documentation for process record and replay
Date: Fri, 17 Oct 2008 10:07:00 -0000	[thread overview]
Message-ID: <uiqrrmt7r.fsf@gnu.org> (raw)
In-Reply-To: <daef60380810162017n15a45d35mee3aea64351b03fc@mail.gmail.com>

> 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.)


  reply	other threads:[~2008-10-17 10:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 15:01 teawater
2008-10-14 16:34 ` Eli Zaretskii
2008-10-15  5:51   ` teawater
2008-10-15  7:24     ` Eli Zaretskii
2008-10-15  7:34       ` teawater
2008-10-15  8:15         ` Eli Zaretskii
2008-10-15  8:41           ` teawater
2008-10-15  9:33             ` Eli Zaretskii
2008-10-15 18:52       ` Michael Snyder
2008-10-15 19:45         ` Eli Zaretskii
2008-10-16  2:10           ` teawater
2008-10-16  7:02             ` Eli Zaretskii
2008-10-16  7:05               ` teawater
2008-10-16  7:35                 ` teawater
2008-10-16 18:42                   ` Eli Zaretskii
2008-10-17  3:18                     ` teawater
2008-10-17 10:07                       ` Eli Zaretskii [this message]
2008-10-17 15:16                         ` teawater
2008-10-17 19:32                         ` Jakob Engblom
2008-10-17 19:44                           ` Michael Snyder
2008-10-17 19:49                           ` Eli Zaretskii
2008-10-18  1:21                             ` teawater
2008-10-18  1:44                             ` teawater
2008-10-22  2:39                             ` teawater
2008-10-22 19:50                               ` Eli Zaretskii
2008-10-23  3:06                                 ` teawater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uiqrrmt7r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox