* gdb.threads/threxit-hop-specific.exp: Use "continue" instead

	of "next" to proceed over pthread_exit call.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 7c3ae15..516efae 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,10 @@
 2010-09-08  Ulrich Weigand  <uweigand@de.ibm.com>
 
+       * gdb.threads/threxit-hop-specific.exp: Use "continue" instead
+       of "next" to proceed over pthread_exit call.
+
+2010-09-08  Ulrich Weigand  <uweigand@de.ibm.com>
+
        * gdb.base/maint.exp: Avoid wildcards against potentially very long
        "maint print statistics" output to prevent expect timeouts.
 

diff --git a/gdb/testsuite/gdb.threads/threxit-hop-specific.exp b/gdb/testsuite/gdb.threads/threxit-hop-specific.exp
index 96b43fe..c2dffc9 100644 (file)
--- a/gdb/testsuite/gdb.threads/threxit-hop-specific.exp
+++ b/gdb/testsuite/gdb.threads/threxit-hop-specific.exp
@@ -52,7 +52,7 @@ gdb_test "break $bpthrline thread 2" \
 set bpexitline [gdb_get_line_number "set exit breakpoint here"]
 gdb_breakpoint "$bpexitline"
 
-gdb_test "next" \
+gdb_test "continue" \
     ".*set exit breakpoint here.*" \
     "get past the thread specific breakpoint"