Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 Hui Zhu <teawater@gmail.com>
Subject: Re: [RFC] testing specifically for process record
Date: Thu, 22 Oct 2009 22:29:00 -0000	[thread overview]
Message-ID: <200910222329.29069.pedro@codesourcery.com> (raw)
In-Reply-To: <4AE0BE00.1030304@vmware.com>

On Thursday 22 October 2009 21:18:08, Michael Snyder wrote:
> Pedro Alves wrote:
> > On Thursday 22 October 2009 20:38:37, Michael Snyder wrote:
> >> gdb_test "record" "" "Turn on process record"
> >> # FIXME: command ought to acknowledge, so we can test if it succeeded.
> > 
> > This can now be switched to gdb_test_multiple, assuming success
> > iff the command was silent, and then followed by "info record"
> > reporting that recording is in effect.  Of course, all
> > that done in a neat reusable function in lib/gdb.exp.  Any
> > takers?  :-)
> > 
> 
> Hmm, that's good... unfortunately "record" will succeed even
> for a remote target, so it doesn't help me with the larger
> problem of detecting remote vs. native.  We want to avoid using
> the process-record commands if we're remote (eg. Simics).

My remark was directed at the FIXME quoted above only.

-- 
Pedro Alves


  reply	other threads:[~2009-10-22 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  0:21 Michael Snyder
2009-10-22 19:45 ` Michael Snyder
2009-10-22 20:17   ` Pedro Alves
2009-10-22 20:24     ` Michael Snyder
2009-10-22 22:29       ` Pedro Alves [this message]
2009-10-26  8:36   ` 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=200910222329.29069.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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