From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Marek Polacek <mpolacek@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:55:00 -0000 [thread overview]
Message-ID: <20110413155532.GA9302@host1.jankratochvil.net> (raw)
In-Reply-To: <4DA5C2F9.908@redhat.com>
Hi Marek,
On Wed, 13 Apr 2011 17:36:25 +0200, Marek Polacek wrote:
> 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.
checked in for you. If you expect more contributions you should consider
write-after-approval sourceware account:
http://sourceware.org/cgi-bin/pdw/ps_form.cgi
> Signed-off-by: Marek Polacek <mpolacek@redhat.com>
FYI this is redundant for GNU projects, FSF copyright assignment covered by
Red Hat in your case applies instead.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2011-04/msg00076.html
--- src/gdb/testsuite/ChangeLog 2011/04/11 17:40:41 1.2661
+++ src/gdb/testsuite/ChangeLog 2011/04/13 15:54:04 1.2662
@@ -1,3 +1,9 @@
+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.
+
2011-04-11 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.python/py-prettyprint.c (struct hint_error): New.
--- src/gdb/testsuite/gdb.base/commands.exp 2011/01/01 15:33:41 1.42
+++ src/gdb/testsuite/gdb.base/commands.exp 2011/04/13 15:54:05 1.43
@@ -704,18 +704,17 @@
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"
next prev parent reply other threads:[~2011-04-13 15:55 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
2011-04-13 15:55 ` Jan Kratochvil [this message]
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=20110413155532.GA9302@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mpolacek@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