after gdb_run_cmd, gdb_expect -> gdb_test_multiple/gdb_test

[thirdparty/binutils-gdb.git] / gdb / testsuite / gdb.arch / i386-size.exp

diff --git a/gdb/testsuite/gdb.arch/i386-size.exp b/gdb/testsuite/gdb.arch/i386-size.exp
index 6d639762ede5092aabaa1a532d6c2c3389cb2f0a..39e5b500e82f837f9a874d6fa208b0d33f7fab3a 100644 (file)
--- a/gdb/testsuite/gdb.arch/i386-size.exp
+++ b/gdb/testsuite/gdb.arch/i386-size.exp
@@ -46,18 +46,7 @@ gdb_load ${binfile}
 # We use gdb_run_cmd so this stands a chance to work for remote
 # targets too.
 gdb_run_cmd
-
-gdb_expect {
-    -re "Program received signal SIGTRAP.*$gdb_prompt $" {
-       pass "run past main"
-    }
-    -re ".*$gdb_prompt $" {
-       fail "run past main"
-    }
-    timeout {
-       fail "run past main (timeout)"
-    }
-}
+gdb_test "" "Program received signal SIGTRAP.*" "run past main"
 
 set message "backtrace shows no function"
 gdb_test_multiple "backtrace 10" $message {