From: Luis Machado <lgustavo@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH] Don't handle timeout inside gdb_test_multiple
Date: Fri, 02 Dec 2016 01:07:00 -0000 [thread overview]
Message-ID: <1480640845-3564-1-git-send-email-lgustavo@codesourcery.com> (raw)
This fixes a few cases where the testcase is explicitly handling timeouts
inside gdb_test_multiple when it is not necessary.
It also converts two gdb_test_multiple calls to gdb_test_no_output calls
(also removing the timeout handling).
gdb/testsuite/ChangeLog:
2016-12-01 Luis Machado <lgustavo@codesourcery.com>
* gdb.base/maint.exp: Remove timeout handling for gdb_test_multiple.
* gdb.cp/gdb2495.exp: Likewise and convert gdb_test_multiple into
gdb_test_no_output for a couple of cases.
* gdb.cp/ovldbreak.exp: Remove timeout handling for gdb_test_multiple.
---
gdb/testsuite/gdb.base/maint.exp | 9 ---------
gdb/testsuite/gdb.cp/gdb2495.exp | 10 ++--------
gdb/testsuite/gdb.cp/ovldbreak.exp | 4 ----
3 files changed, 2 insertions(+), 21 deletions(-)
diff --git a/gdb/testsuite/gdb.base/maint.exp b/gdb/testsuite/gdb.base/maint.exp
index b07b370..17c606b 100644
--- a/gdb/testsuite/gdb.base/maint.exp
+++ b/gdb/testsuite/gdb.base/maint.exp
@@ -297,9 +297,6 @@ gdb_test_multiple "maint print msymbols msymbols_output2 ${testfile}" "maint pri
-re ".*$gdb_prompt $" {
fail "maint print msymbols"
}
- timeout {
- fail "(timeout) maint print msymbols"
- }
}
gdb_test "shell rm -f msymbols_output2" ".*" \
"shell rm -f msymbols_output2"
@@ -307,17 +304,11 @@ gdb_test_multiple "maint print msymbols msymbols_output2 ${testfile}" "maint pri
-re ".*$gdb_prompt $" {
fail "maint print msymbols"
}
- timeout {
- fail "(timeout) maint print msymbols"
- }
}
}
-re ".*$gdb_prompt $" {
fail "maint print msymbols"
}
- timeout {
- fail "(timeout) maint print msymbols"
- }
}
gdb_test "cd ${mydir}" \
"Working directory [string_to_regexp ${mydir}]\..*" \
diff --git a/gdb/testsuite/gdb.cp/gdb2495.exp b/gdb/testsuite/gdb.cp/gdb2495.exp
index b4304fb..ac74382 100644
--- a/gdb/testsuite/gdb.cp/gdb2495.exp
+++ b/gdb/testsuite/gdb.cp/gdb2495.exp
@@ -117,10 +117,7 @@ if ![runto_main] then {
# behaviour; it should not. Test both on and off states.
# Turn on unwind on signal behaviour.
-gdb_test_multiple "set unwindonsignal on" "turn unwindonsignal on" {
- -re "$gdb_prompt $" {pass "set unwindonsignal on"}
- timeout {fail "(timeout) set unwindonsignal on"}
-}
+gdb_test_no_output "set unwindonsignal on"
# Check that it is turned on.
gdb_test "show unwindonsignal" \
@@ -133,10 +130,7 @@ gdb_test "p exceptions.raise_signal(1)" \
"To change this behavior use \"set unwindonsignal off\".*"
# And reverse - turn off again.
-gdb_test_multiple "set unwindonsignal off" "turn unwindonsignal off" {
- -re "$gdb_prompt $" {pass "set unwindonsignal off"}
- timeout {fail "(timeout) set unwindonsignal off"}
-}
+gdb_test_no_output "set unwindonsignal off"
# Check that it is actually turned off.
gdb_test "show unwindonsignal" \
diff --git a/gdb/testsuite/gdb.cp/ovldbreak.exp b/gdb/testsuite/gdb.cp/ovldbreak.exp
index 96d3bd3..b6c5efd 100644
--- a/gdb/testsuite/gdb.cp/ovldbreak.exp
+++ b/gdb/testsuite/gdb.cp/ovldbreak.exp
@@ -58,10 +58,6 @@ proc take_gdb_out_of_choice_menu {} {
gdb_test_multiple " " " " {
-re ".*$gdb_prompt $" {
}
- timeout {
- perror "could not resynchronize to command prompt (timeout)"
- continue
- }
}
}
--
2.7.4
next reply other threads:[~2016-12-02 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 1:07 Luis Machado [this message]
2016-12-02 2:42 ` Joel Brobecker
2016-12-02 4:09 ` Luis Machado
2016-12-02 11:04 ` Pedro Alves
2016-12-02 15:25 ` Luis Machado
2016-12-02 15:42 ` Pedro Alves
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=1480640845-3564-1-git-send-email-lgustavo@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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