From: Fernando Nasser <fnasser@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, mec@shout.net
Subject: Re: [RFA/testsuite] Re: RFC: gdb_test_multiple
Date: Tue, 14 Jan 2003 19:16:00 -0000 [thread overview]
Message-ID: <3E2461F1.7080900@redhat.com> (raw)
In-Reply-To: <20030107171034.GA22300@nevyn.them.org>
Hi Daniel,
I am _much_ more comfortable with this version. Thanks for spending the time to
get it into this format.
I believe Michael wanted to give it a spin, but otherwise I think it is ripe to
be committed.
Thanks to Andrew and Michael for helping with comments. I was away and just
came back yesterday.
Regards to all,
Fernando
Daniel Jacobowitz wrote:> On Mon, Jan 06, 2003 at 10:33:11PM -0600, Michael
Elizabeth Chastain wrote:
>
>>>OK. I'll have an even easier version of this done tomorrow; it has one
>>>truely gruesome TCL hack in it, but that's it.
>>
>>I'd like to do another test spin on the new version before you commit
>>it if that's all right with you. I can do a cut-down version but I'd
>>like to be really sure about sourceware dejagnu because the damn things
>>are subtly different, and I normally don't test with it.
>
>
> Here's the version I'd like to include. I definitely need your
> reaction to this patch, and Fernando's. I'd like anyone else's, too.
> There's one quoting hack in it, but I don't think it's fragile.
>
> This one is a lot more intuitive. You use it like this:
>
> gdb_test_multiple $command $message {
> -re "\[\r\n\]*($pattern)\[\r\n\]+$gdb_prompt $" {
> if ![string match "" $message] then {
> pass "$message"
> }
> }
> -re "(${question_string})$" {
> send_gdb "$response_string\n";
> exp_continue;
> }
> }
>
> There's no magic variable names any more. $pattern and $gdb_prompt in
> this example get evaluated in the caller's context; the action blocks
> get executed in the caller's context; and in general it behaves just
> like expect ought to.
>
> [That "\[\r\n\]*" is just there because it was previously in gdb_test.
> Bonus points to the astute reader who can figure out why it doesn't
> need to be there. Presumably the _intent_ was to use "\[\r\n\]+", so
> that $pattern needed to match an entire line, but our testsuite doesn't
> honor that intent, so this is a question for another day.]
>
> Fernando, Michael, how does this look? I think it will be useful.
>
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2003-01-14 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 4:33 Michael Elizabeth Chastain
2003-01-07 17:10 ` [RFA/testsuite] " Daniel Jacobowitz
2003-01-14 19:16 ` Fernando Nasser [this message]
2003-01-23 1:36 ` Daniel Jacobowitz
2003-01-07 17:21 Michael Elizabeth Chastain
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=3E2461F1.7080900@redhat.com \
--to=fnasser@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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