Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
		GDB Patches <gdb-patches@sourceware.org>,
		Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [rfc] Fix info spu mailbox command
Date: Wed, 19 Mar 2008 11:54:00 -0000	[thread overview]
Message-ID: <20080319115354.GA32034@caradoc.them.org> (raw)
In-Reply-To: <47E0EAB3.5080703@de.ibm.com>

On Wed, Mar 19, 2008 at 11:28:03AM +0100, Markus Deuling wrote:
> Hi Joel,
>
> Joel Brobecker schrieb:
>> Any reason for not using gdb_test_multiple in this case (instead of
>> send_gdb/gdb_expext)? gdb_test_multiple has been designed to handle
>> this type of test, and as a bonus, you won't have to handle the timeout
>> explicitly.
>>
>
> as far as I see gdb_expect is much more often used compared to 
> gdb_test_multiple. What is the advantage of gdb_test_multiple compared to 
> just send/expect? 

gdb_test_multiple is newer and most of the testsuite is very old,
that's why gdb_expect is used.  gdb_test_multiple is much better
because it handles standard cases, like an unexpected prompt, without
having to wait for a timeout.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-19 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  6:27 Markus Deuling
2008-03-17 13:23 ` Ulrich Weigand
2008-03-18 19:53   ` Markus Deuling
2008-03-18 21:25     ` Joel Brobecker
2008-03-19 10:28       ` Markus Deuling
2008-03-19 11:54         ` Daniel Jacobowitz [this message]
2008-03-19 18:01           ` Markus Deuling
2008-03-19 18:33             ` Joel Brobecker
2008-03-19 18:50               ` Markus Deuling
2008-03-19 21:12                 ` Ulrich Weigand

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=20080319115354.GA32034@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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