2011-10-28 Pedro Alves <pedro@codesourcery.com>

[binutils-gdb.git] / gdb / testsuite / gdb.threads / threadapply.exp

diff --git a/gdb/testsuite/gdb.threads/threadapply.exp b/gdb/testsuite/gdb.threads/threadapply.exp
index 612c8a55b9e968fa7f5c66c7a6c54fb92c6b4ebb..5ba8286d4e244522ee679e4a727bba91ed15e6df 100644 (file)
--- a/gdb/testsuite/gdb.threads/threadapply.exp
+++ b/gdb/testsuite/gdb.threads/threadapply.exp
@@ -1,6 +1,6 @@
 # This testcase is part of GDB, the GNU debugger.
 
-# Copyright 2004, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
+# Copyright 2004, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -19,8 +19,6 @@ if $tracelevel {
     strace $tracelevel
 }
 
-set prms_id 0
-set bug_id 0
 
 # This test verifies that a macro using backtrace can be applied to all threads
 # and will continue for each thread even though an error may occur in
@@ -48,7 +46,7 @@ if ![runto_main] then {
 
 # Break after all threads have been started.
 set break_line [gdb_get_line_number "Break here"]
-gdb_test "b $break_line" ""
+gdb_test "b $break_line" ".*"
 gdb_test "continue"
 
 gdb_test_multiple "define backthread" "defining macro" {
@@ -65,7 +63,7 @@ gdb_test_multiple "define backthread" "defining macro" {
 # Cause backtraces to fail by setting a limit.  This allows us to
 # verify that the macro can get past the backtrace error and perform
 # subsequent commands.
-gdb_test "set backtrace limit 3" ""
+gdb_test_no_output "set backtrace limit 3"
 gdb_test "thread apply all backthread" "Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14"
 
 # Go into the thread_function to check that a simple "thread apply"