Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] gdb.cp/static-print-quit.exp: fix racy tests (PR testsuite/12649)
Date: Fri, 06 May 2011 08:58:00 -0000	[thread overview]
Message-ID: <4DC3B82D.1000505@redhat.com> (raw)
In-Reply-To: <20110506021511.GA30222@host1.jankratochvil.net>

On 05/06/2011 04:15 AM, Jan Kratochvil wrote:
> exp_continue/variables make it complicated, I would prefer splitting it to
> multiple consecutive test cases.

Yep, splitting the case was apparently the right thing to do.  What a shame
that this didn't occurred to me before.  Thanks.

> BTW you do not need to match exactly "<return>" as is in lib/gdb.exp - it is
> enough to match any string ending with "<return>".

OK, I wish I knew this before :-).

> FYI the diff could not be applied as it has <tab>s converted to spaces.

Right, sorry.

> Any comments?  I will check it in otherwise.

I tested your patch and all seems fine.  Maybe just, I think here:

> +set test "print c - q <return>"
> +gdb_test_multiple "" $test {
> +    -re " to continue, or q <return>" {

and here:

> +set test "print c - to quit"
> +gdb_test_multiple "" $test {
>      -re " to quit---$" {

the `-re' are in fact not needed since we don't use any regexps in the
string.  However, they certainly do no harm so no need to remove them.
Thanks again, Jan.

	Marek	


  reply	other threads:[~2011-05-06  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 18:03 Marek Polacek
2011-05-05 18:12 ` Marek Polacek
2011-05-06  2:15 ` Jan Kratochvil
2011-05-06  8:58   ` Marek Polacek [this message]
2011-05-06 11:09     ` Pierre Muller
2011-05-06 11:15       ` Marek Polacek
2011-05-06 13:41     ` Jan Kratochvil

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=4DC3B82D.1000505@redhat.com \
    --to=mpolacek@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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