Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	  "gdb@sourceware.org" <gdb@sourceware.org>,
	 Hui Zhu <teawater@gmail.com>
Subject: Re: Testing of reverse debug commands
Date: Sun, 12 Jul 2009 17:19:00 -0000	[thread overview]
Message-ID: <4A5A19FC.9050206@vmware.com> (raw)
In-Reply-To: <20090712142834.GA3355@host0.dyn.jankratochvil.net>

Jan Kratochvil wrote:
> On Sun, 12 Jul 2009 10:01:45 +0200, Joel Brobecker wrote:
>>>     gdb_test "record" "" "Turn on process record"
>>>     # FIXME: command ought to acknowledge, so we can test if it succeeded.
>> This is just a shot in the dark since I really don't have much time
>> to double-check this, but does gdb_test_multiple allow you to verify
>> that no output was generated? For some reason, I thought it did.
> 
> This one works but not sure if it cannot have some problems:
> 
> set cmd "set verbose 0"
> gdb_test $cmd "[string_to_regexp $cmd]"

Hmm, ok, three people so far have responded with
work-arounds (thanks).

Does that mean y'all lean toward NOT making the
commands generate some output of their own?

Now would be the time to decide, before the first official release...


  reply	other threads:[~2009-07-12 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12  0:44 Michael Snyder
2009-07-12  8:02 ` Joel Brobecker
2009-07-12 14:20   ` Pedro Alves
2009-07-12 14:29   ` Jan Kratochvil
2009-07-12 17:19     ` Michael Snyder [this message]
2009-07-12 18:19       ` Joel Brobecker
2009-07-12 18:25       ` Pedro Alves
2009-07-12 18:50       ` Marc Khouzam
2009-07-12 19:07         ` Pedro Alves
2009-07-12 19:26           ` Marc Khouzam

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=4A5A19FC.9050206@vmware.com \
    --to=msnyder@vmware.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.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