From: Michael Snyder <msnyder@vmware.com>
To: teawater <teawater@gmail.com>
Cc: moueza <mouezapeter@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA reverse] Process record and replay target user docs for gdb manual
Date: Thu, 11 Dec 2008 17:57:00 -0000 [thread overview]
Message-ID: <49415356.3020804@vmware.com> (raw)
In-Reply-To: <daef60380812102219g2ff7959ct95039d84052a9320@mail.gmail.com>
Hui, is the branch still in good shape?
Peter, you should be able to check out a cvs branch that has this stuff,
using the anon-cvs instructions here:
http://sourceware.org/gdb/current/
and the branch name "reverse-20080930-branch".
teawater wrote:
> Hi moueza,
>
> P record is in the process of submit.
> You can get the patch for cvs-head from this maillist.
>
> Thanks,
> Hui
>
> On Thu, Dec 11, 2008 at 13:52, moueza <mouezapeter@gmail.com> wrote:
>> hi,
>> Could you give me a link where I could download this gdb record reverse
>> program?
>>
>>
>> Michael Snyder-6 wrote:
>>> Hi Eli --
>>>
>>> teawater has implemented a record/replay functionality for native
>>> linux gdb. It is one of four targets now that use my reverse debug
>>> patch.
>>>
>>> The plan is for his patches to be submitted once mine have been accepted.
>>> Meanwhile he and I have been collaborating on a cvs branch.
>>>
>>> Michael
>>>
>>> ________________________________________
>>> From: gdb-patches-owner@sourceware.org [gdb-patches-owner@sourceware.org]
>>> On Behalf Of Eli Zaretskii [eliz@gnu.org]
>>> Sent: Thursday, October 02, 2008 11:25 PM
>>> To: teawater
>>> Cc: gdb-patches@sourceware.org
>>> Subject: Re: [RFA reverse] Process record and replay target user docs for
>>> gdb manual
>>>
>>>> Date: Thu, 2 Oct 2008 17:23:57 +0800
>>>> From: teawater <teawater@gmail.com>
>>>>
>>>> This is process record and replay target user manual.
>>> Thank you.
>>>
>>> Please remind me the context of this text. Does it describe
>>> additional aspects of the patches posted just yesterday by Michael
>>> Snyder? Or does it describe some other GDB feature? Or something
>>> else?
>>>
>>> Armed with that knowledge, I will know what to do with this text and
>>> when.
>>>
>>> Thanks.
>>>
>>>
>> --
>> View this message in context: http://www.nabble.com/-RFA-reverse--Process-record-and-replay-target-user-docs-for-gdb-manual-tp19776067p20949851.html
>> Sent from the Sourceware - gdb-patches mailing list archive at Nabble.com.
>>
>>
prev parent reply other threads:[~2008-12-11 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 9:24 teawater
2008-10-03 6:26 ` Eli Zaretskii
2008-10-03 9:15 ` teawater
2008-10-03 10:06 ` Eli Zaretskii
2008-10-03 15:46 ` Michael Snyder
2008-12-11 5:53 ` moueza
2008-12-11 6:20 ` teawater
2008-12-11 17:57 ` Michael Snyder [this message]
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=49415356.3020804@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=mouezapeter@gmail.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