From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches@sourceware.org, drow@false.org,
pedro@codesourcery.com, teawater@gmail.com
Subject: Re: [RFA] Reverse Debugging, 5/5
Date: Fri, 03 Oct 2008 06:35:00 -0000 [thread overview]
Message-ID: <ufxnei3ud.fsf@gnu.org> (raw)
In-Reply-To: <48E54E35.6090906@vmware.com>
> Date: Thu, 02 Oct 2008 15:41:57 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> "drow@false.org" <drow@false.org>,
> "pedro@codesourcery.com" <pedro@codesourcery.com>,
> "teawater@gmail.com" <teawater@gmail.com>
>
> Here's a revised patch for the doc only.
> I added a footnote about side effects, and
> followed your other suggestions.
Thanks. I have only one minor comment this time:
> +The contract between @value{GDBN} and the reverse executing target
> +requires only that the target do something reasonable when
> +@value{GDBN} tells it to execute backwards, and then report the
> +results back to @value{GDBN}. Whatever the target reports back to
> +@value{GDBN}, @value{GDBN} will report back to the user. We assume
> +that the memory and registers that the target reports to us are in a
> +consistant state, but we accept whatever we are given.
This text switches from "GDB" to "we" in mid-air. I'd prefer to stay
with "GDB", as it will not be very clear to the reader who are "we" ;-)
next prev parent reply other threads:[~2008-10-03 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:21 Michael Snyder
2008-10-02 19:49 ` Eli Zaretskii
2008-10-02 21:42 ` Michael Snyder
2008-10-03 6:30 ` Eli Zaretskii
2008-10-03 18:07 ` Michael Snyder
2008-10-04 8:13 ` Eli Zaretskii
2008-10-04 17:56 ` Michael Snyder
2008-10-02 22:43 ` Michael Snyder
2008-10-03 6:35 ` Eli Zaretskii [this message]
2008-10-02 22:54 ` Michael Snyder
2008-10-03 6:25 ` Eli Zaretskii
2008-10-03 17:45 ` Daniel Jacobowitz
2008-10-03 17:58 ` Michael Snyder
2008-10-07 3:30 ` Joel Brobecker
2008-10-07 18:25 ` Michael Snyder
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=ufxnei3ud.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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