From: Hui Zhu <teawater@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Michael Snyder <msnyder@vmware.com>,
Thiago Jung Bauermann <bauerman@br.ibm.com>,
Eli Zaretskii <eliz@gnu.org>,
paawan1982@yahoo.com
Subject: Re: [RFA] Submit process record and replay fourth time, 0/8
Date: Wed, 25 Mar 2009 09:02:00 -0000 [thread overview]
Message-ID: <daef60380903250023h3bfd7068gef837333443c09a4@mail.gmail.com> (raw)
In-Reply-To: <daef60380903210858l5e7868d6g7ce240459c00bae3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]
Some update.
On Sat, Mar 21, 2009 at 23:58, Hui Zhu <teawater@gmail.com> wrote:
> Hi guys,
>
> After third time submit, there are a lot of change with process record
> and replay. So I submit fourth time to make it clear to review.
>
> For this time, Most of changes were updated follow cvs head and a lot
> of format fixes. Patch for target.c was removed. Record.c was
> updated a lot of parts according to the ideas of Pedro (Much
> appreciated).
> Thanks for help of everybody in the maillist.
>
> Process record and replay make gdb can record inferior execute log and
> replay (include reverse debug).
> Now, it support I386-Linux single-thread inferior native debug.
>
> I've divided this patch into eight sections, for ease of review.
> They group as:
> 1) Architecture support layer (gdbarch.sh, gdbarch.c, gbarch.h).
> 2) New stratum of strata in target layer (target.h).
> 3) Process record and replay target (record.c, record.h, Makefile.in).
> 4) Process record and replay for Linux (linux-record.c,
> linux-record.h, Makefile.in, configure.tgt).
> 5) Event handling (infrun.c).
> 6) Intel 386 target-dependent stuff (i386-tdep.c, i386-tdep.h).
> 7) Target-dependent code for GNU/Linux i386 (i386-linux-tdep.c).
> 8) User interface and documentation.
>
> For the NEWS:
> * Process record and replay
>
> In a architecture environment that supports ``process record and
> replay'', ``process record and replay'' target can record a log of
> the process execution, and replay it with both forward and reverse
> execute commands.
>
> These patches be tested with testsuite gdb.twreverse in branch
> reverse-20081226-branch.
>
> Attachment is the compressed patches package to make get all patches easy.
>
> Thanks,
> Hui
>
[-- Attachment #2: prec41.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 25302 bytes --]
next prev parent reply other threads:[~2009-03-25 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 15:59 Hui Zhu
2009-03-25 9:02 ` Hui Zhu [this message]
2009-04-02 14:26 ` Pedro Alves
2009-04-15 16:56 ` Hui Zhu
2009-04-21 13:31 ` Pedro Alves
2009-04-22 9:03 ` Hui Zhu
2009-04-28 10:24 ` Hui Zhu
2009-04-28 13:50 ` Marc Khouzam
2009-04-28 15:15 ` Hui Zhu
2009-03-30 8:35 ` Hui Zhu
2009-03-30 14:28 ` Marc Khouzam
2009-03-30 15:29 ` Hui Zhu
2009-03-30 15:33 ` Marc Khouzam
2009-03-30 15:34 ` Hui Zhu
2009-03-30 15:52 ` Marc Khouzam
2009-04-01 4:53 ` Hui Zhu
2009-04-02 12:48 ` Hui Zhu
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=daef60380903250023h3bfd7068gef837333443c09a4@mail.gmail.com \
--to=teawater@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=pedro@codesourcery.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