diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 3f41178dd15..6f97edad8c8 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2015-03-04 Pedro Alves + + * gdb.threads/thread-specific-bp.exp: Delete "info threads" test. + 2015-03-04 Mark Kettenis * gdb.base/foll-fork.exp: Enable on *-*-openbsd*. diff --git a/gdb/testsuite/gdb.threads/thread-specific-bp.exp b/gdb/testsuite/gdb.threads/thread-specific-bp.exp index e167564558c..c4d828655cc 100644 --- a/gdb/testsuite/gdb.threads/thread-specific-bp.exp +++ b/gdb/testsuite/gdb.threads/thread-specific-bp.exp @@ -91,19 +91,6 @@ proc check_thread_specific_breakpoint {mode} { "Breakpoint .* end .* at .*" \ "continue to end" - # Force GDB to update the thread list. Otherwise, depending - # on target, GDB may not realize that the start thread has - # exited and thus not remove the thread specific breakpoint. - set test "thread start is gone" - gdb_test_multiple "info threads" $test { - -re "\[0-9\]+.*start.*$gdb_prompt $" { - fail $test - } - -re "$gdb_prompt $" { - pass $test - } - } - set test "thread-specific breakpoint was deleted" gdb_test_multiple "info breakpoint" $test { -re "thread $start_thre\n$gdb_prompt $" {