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
Subject: Re: [PATCH] gdb.base/commands.exp: fix racy test (PR testsuite/12649)
Date: Wed, 13 Apr 2011 15:36:00 -0000	[thread overview]
Message-ID: <4DA5C2F9.908@redhat.com> (raw)
In-Reply-To: <20110413092029.GA19366@host1.jankratochvil.net>

On 04/13/2011 11:20 AM, Jan Kratochvil wrote:
> I would prefer one re-post before the approval.

Sure!  Thanks for review.  Here's amended version (if there's still anything that
could be improved, just tell me):

2011-04-13  Marek Polacek  <mpolacek@redhat.com>

        * gdb.base/commands.exp (redefine_backtrace_test): Fix race. 
        New testcase `expect response to define backtrace'.  Also remove
        redundant `default' block.

Signed-off-by: Marek Polacek <mpolacek@redhat.com>
---
 gdb/testsuite/gdb.base/commands.exp |   15 +++++++--------
 1 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/gdb/testsuite/gdb.base/commands.exp b/gdb/testsuite/gdb.base/commands.exp
index 3bff053..a0ac25b 100644
--- a/gdb/testsuite/gdb.base/commands.exp
+++ b/gdb/testsuite/gdb.base/commands.exp
@@ -704,18 +704,17 @@ proc redefine_backtrace_test {} {
     global gdb_prompt
 
     gdb_test_multiple "define backtrace" "define backtrace" {
-	-re "Really redefine built-in.*$" {
-	    send_gdb "y\n"
-	    exp_continue
+	-re "Really redefine built-in command \"backtrace\"\\? \\(y or n\\) $"  {
+	    pass "define backtrace"
 	}
+    }
 
-	-re "End with"  {
-	    pass "define backtrace in redefine_backtrace_test"
-	}
-        default {
-	    fail "(timeout or eof) define backtrace in redefine_backtrace_test"
+    gdb_test_multiple "y" "expect response to define backtrace" {
+	-re "End with a line saying just \"end\"\\.\r\n>$"  {
+	    pass "expect response to define backtrace"
 	}
     }
+
     gdb_test "echo hibob\\n\nend" \
 	    "" \
 	    "enter commands in redefine_backtrace_test"
-- 
1.7.3.4


  reply	other threads:[~2011-04-13 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  7:58 [PATCH] gdb.base/commands.exp: fix racy test Marek Polacek
2011-04-13  8:55 ` Andreas Schwab
2011-04-13  9:20 ` [PATCH] gdb.base/commands.exp: fix racy test (PR testsuite/12649) Jan Kratochvil
2011-04-13 15:36   ` Marek Polacek [this message]
2011-04-13 15:55     ` Jan Kratochvil
2011-04-13 16:11       ` Marek Polacek
2011-04-13 17:28         ` 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=4DA5C2F9.908@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