Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Michael Snyder" <msnyder@specifix.com>
Cc: "Pedro Alves" <pedro@codesourcery.com>,
	gdb-patches@sourceware.org,
	 	"Thiago Jung Bauermann" <bauerman@br.ibm.com>
Subject: Re: GDB record patch 0.1.3.1 for GDB-6.8 release
Date: Thu, 12 Jun 2008 18:10:00 -0000	[thread overview]
Message-ID: <daef60380806112250m4d0fda2ybf4d80f069a81e10@mail.gmail.com> (raw)
In-Reply-To: <1213204275.3601.605.camel@localhost.localdomain>

Thanks Michael,

I've got it and read it. :)

Hui

On Thu, Jun 12, 2008 at 01:11, Michael Snyder <msnyder@specifix.com> wrote:
> On Wed, 2008-06-11 at 15:45 +0800, teawater wrote:
>> Hi Pedro,
>>
>> > Don't worry, it's really more about code reorganization, than
>> > rewriting.  :-)
>> >
>> > You have two major components in your patch.
>> >
>> >  1 - The record/replay component
>> >  2 - The inferior control in reverse execution mode.
>> >
>> > I'm suggesting to split those up, and make them communicate
>> > with an abstracted interface (target methods).  In addition,
>> > make the record support a layer on top of the
>> > forward-execution-only debugging targets (of course, defering
>> > much to the arch support).
>> >
>> Michael Snyder is think about it too. He make a rev interface in
>> before. I will try to use it.
>
> Hui,
>
> I've created a new branch in which I've hoisted my old
> reverse-debugging changes into the current codebase.
> It compiles, but I haven't had a chance to test it yet
> to see if it actually works in reverse.
>
> You might like to take a look at it, to get an idea of
> the direction we were most recently headed -- maybe diff
> it against the base to look at the changes.
>
> Branch name: msnyder-reverse-20080609-branch
>
>
>
>


  reply	other threads:[~2008-06-12  5:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  8:55 Tea
2008-05-20  4:33 ` Thiago Jung Bauermann
2008-05-20  6:38   ` Daniel Jacobowitz
2008-05-20 15:32     ` Tea
2008-05-20 18:51       ` Michael Snyder
2008-05-21 17:26         ` Tea
2008-05-20 15:33   ` Tea
2008-05-21 17:14   ` Tea
2008-05-21 22:01     ` Michael Snyder
2008-05-21 22:16       ` Thiago Jung Bauermann
2008-05-21 22:40         ` Daniel Jacobowitz
2008-05-22 15:08           ` Thiago Jung Bauermann
2008-05-23  2:54             ` Tea
2008-05-23  4:33               ` Michael Snyder
2008-05-23 14:33                 ` Tea
2008-05-23 16:46                   ` Michael Snyder
2008-05-23 18:16                     ` Tea
2008-05-23  3:52 ` Pedro Alves
2008-05-23 14:31   ` Tea
2008-05-23 21:10     ` Pedro Alves
2008-06-08  6:53       ` teawater
2008-06-09  0:52         ` Pedro Alves
2008-06-09  3:00           ` Daniel Jacobowitz
2008-06-09 13:58             ` Thiago Jung Bauermann
2008-06-10  2:04               ` Michael Snyder
2008-06-09 22:56             ` Michael Snyder
2008-06-11 11:59           ` teawater
2008-06-11 20:03             ` Michael Snyder
2008-06-12 18:10               ` teawater [this message]
2008-06-13  6:08                 ` Michael Snyder
2008-06-14  6:24                   ` teawater
2008-06-14 10:31                     ` Michael Snyder
2008-06-15  3:27                       ` 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=daef60380806112250m4d0fda2ybf4d80f069a81e10@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@specifix.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