Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	  teawater <teawater@gmail.com>
Subject: Re: [RFA] Resubmit process record and replay, 6/10
Date: Thu, 20 Nov 2008 08:04:00 -0000	[thread overview]
Message-ID: <4924C6D5.5020903@vmware.com> (raw)
In-Reply-To: <200811200202.26043.pedro@codesourcery.com>

Pedro Alves wrote:
> On Thursday 20 November 2008 01:55:39, Michael Snyder wrote:
>> 1) Instead of "RECORD_IS_USED", how about "TARGET_IS_PROCESS_RECORD"?
>>
>> 2) Instead of "record_not_record_set", how about "record_skip_recording"?
>>
> 
> OOC, did you guys consider investigating replacing this a
> bit further?
> 
> Instead of querying if the target is XXXX, query for target has
> property(ies) YYYY or is in state WWW.
> 
> This is my knee-jerk reaction to making the core side know about a
> specific target.
> 

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".



  reply	other threads:[~2008-11-20  2:10 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 [this message]
2008-11-20  8:08       ` Pedro Alves
2008-11-24 16:45         ` teawater
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=4924C6D5.5020903@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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