From: teawater <teawater@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 9/10
Date: Thu, 20 Nov 2008 14:29:00 -0000 [thread overview]
Message-ID: <daef60380811192127k1c0d5ad5m2908e75a8fefd8b8@mail.gmail.com> (raw)
In-Reply-To: <4924C5F6.8090800@vmware.com>
This patch is in 9-i386-linux-tdep.txt.
I want to add "diff with the previous patch" to make RFA clear. Now, I
think it make rfa not clear. Sorry for that.
On Thu, Nov 20, 2008 at 10:05, Michael Snyder <msnyder@vmware.com> wrote:
> teawater wrote:
>>
>> This patch add code make process record and replay can record I386
>> Linux system call execute log.
>>
>> 2008-11-16 Hui Zhu <teawater@gmail.com>
>>
>> I386 Linux process record and replay support.
>>
>> * i386-linux-tdep.c (linux_record_tdep): New variable. This
>> struct has the argument for the function
>> "record_linux_system_call".
>> (i386_linux_intx80_sysenter_record): New function. Parse the
>> system call instruction and call function
>> "record_linux_system_call" record execute log.
>
> ... to record an execution log.
>
>> (i386_linux_init_abi): Initialize "linux_record_tdep". Set
>> "i386_linux_intx80_sysenter_record" to "i386_intx80_record"
>> and "i386_sysenter_record".
>>
>> i386-linux-tdep.c | 318
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 318 insertions(+)
>>
>> Following is the diff with the previous patch:
>
> And again, don't know how others feel, but I personally would
> rather see the diff against the current cvs state.
>
> With, if appropriate, a short verbal description of changes
> since the previous patch.
>
> If I'm wrong about the group preference, ok. ;-)
>
next prev parent reply other threads:[~2008-11-20 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 9:28 teawater
2008-11-20 6:14 ` Michael Snyder
2008-11-20 14:29 ` teawater [this message]
2008-11-20 14:51 ` Michael Snyder
2008-11-20 17:09 ` 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=daef60380811192127k1c0d5ad5m2908e75a8fefd8b8@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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