From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: teawater@gmail.com, gdb-patches@sourceware.org
Subject: Re: [reverse RFC] Add documentation for process record and replay
Date: Wed, 15 Oct 2008 19:45:00 -0000 [thread overview]
Message-ID: <uej2hod8w.fsf@gnu.org> (raw)
In-Reply-To: <48F63B15.3070705@vmware.com>
> Date: Wed, 15 Oct 2008 11:48:53 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: teawater <teawater@gmail.com>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> Eli, I think the relation is that we will save one log entry
> for each instruction executed. Not necessarily that we save
> the instruction itself, but since we do save the PC (it being
> part of the state that is changed by executing the instruction),
> we always have access to the instruction itself if we want it
> (either in memory or in object file).
I understand that (now). But the original text, viz.
When this target is in use, if the next instruction to be executed
is in the execution log, ...
^^^^^^^^^^^^^^^^^^^^^^^
made it sound like the instructions themselves are in the log. This
will need to be rephrased.
next prev parent reply other threads:[~2008-10-15 19:45 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 [this message]
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
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=uej2hod8w.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