Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Michael Snyder <msnyder@vmware.com>
Subject: Re: [rfa] gdb.base/volatile.exp / varargs.exp: replace send_gdb with gdb_test
Date: Thu, 20 May 2010 16:42:00 -0000	[thread overview]
Message-ID: <20100520163130.GB3019@adacore.com> (raw)
In-Reply-To: <201005201724.42637.pedro@codesourcery.com>

> You can anchor the output with gdb_test_multiple.  This, for example,
> checks that a command produces no output other than the prompt:
> 
>     set cmd "..."
>     set msg "..."
>     set cmd_regex [string_to_regexp $cmd]
>     gdb_test_multiple $cmd $msg {
>         -re "^$cmd_regex\r\n$gdb_prompt $" {
>             pass $msg
>         }
>     }

Good to know! I thought I tried the above, but I must have screwed
up somewhere - maybe I was missing the \r\n...

> something like this is used in several places in the
> testsuite.  we could perhaps add a wrapper in gdb.exp.

I think we should - it's something that is so common, and the
gdb.reverse section alone is littered with FIXMEs because of
this issue. gdb_test_no_output?

-- 
Joel


  reply	other threads:[~2010-05-20 16:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 20:54 Michael Snyder
2010-05-20 16:13 ` Joel Brobecker
2010-05-20 16:31   ` Pedro Alves
2010-05-20 16:42     ` Joel Brobecker [this message]
2010-05-20 16:47       ` Pedro Alves
2010-05-20 17:09         ` Joel Brobecker
2010-05-20 17:57           ` Pedro Alves
2010-05-20 18:08           ` Michael Snyder
2010-05-20 19:45             ` [commit/testsuite] lib/gdb.exp: New gdb_test_no_output function Joel Brobecker
2010-05-20 18:04   ` [rfa] gdb.base/volatile.exp / varargs.exp: replace send_gdb with gdb_test Michael Snyder
2010-05-20 18:40     ` Joel Brobecker

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=20100520163130.GB3019@adacore.com \
    --to=brobecker@adacore.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