From: teawater <teawater@gmail.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: "Michael Snyder" <msnyder@vmware.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 6/10
Date: Mon, 24 Nov 2008 16:45:00 -0000 [thread overview]
Message-ID: <daef60380811231923v5c9ff8a8s3b4f39ecdef9a5a0@mail.gmail.com> (raw)
In-Reply-To: <200811200214.37330.pedro@codesourcery.com>
On Thu, Nov 20, 2008 at 10:14, Pedro Alves <pedro@codesourcery.com> wrote:
> On Thursday 20 November 2008 02:09:25, Michael Snyder wrote:
>
>> I do share your knee jerk reaction...
>>
>> Maybe I "let the cat out of the bag", because it appears
>> that the intended meaning of the macro was "are we recording",
>> but the implementation is "is this the process_record target".
>
> I already felt like this before regarding the RECORD_IS_USED macro,
> so it was not about the name change.
>
> Not sure if it's "are we recording" or are we "replaying", or
> a mix of both. In any case, could each call site on the common
> code be replaced by a new suitable target method/property?
Could you give me more message on it? I am not very clear your mean.
Thanks,
Hui
next prev parent reply other threads:[~2008-11-24 3:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 2:27 teawater
2008-11-20 4:48 ` Michael Snyder
2008-11-20 5:27 ` Pedro Alves
2008-11-20 8:04 ` Michael Snyder
2008-11-20 8:08 ` Pedro Alves
2008-11-24 16:45 ` teawater [this message]
2008-11-26 17:25 ` Pedro Alves
2008-11-26 20:44 ` teawater
2008-11-24 17:32 ` teawater
2008-11-24 21:54 ` Michael Snyder
2008-11-25 17:47 ` teawater
2008-11-26 15:55 ` Michael Snyder
2008-11-26 19:32 ` teawater
2008-12-05 3:35 ` teawater
2008-12-11 3:43 ` teawater
2008-12-19 7:26 ` 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=daef60380811231923v5c9ff8a8s3b4f39ecdef9a5a0@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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