Fix multiple-successive-infcall.exp with gdbserver

PR gdb/33791 points out that my recent change to emit the thread ID in
the thread notification message broke multiple-successive-infcall.exp
when run with gdbserver.  This patch fixes the oversight.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33791
Approved-By: Simon Marchi <simon.marchi@efficios.com>

diff --git a/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp b/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp
index ae3bcee0bee599f49051b9164423ca0479f08b59..732793010ef863909baceff4c5e080fbc774db1c 100644 (file)
--- a/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp
+++ b/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp
@@ -40,7 +40,7 @@ foreach_with_prefix thread {5 4 3}  {
     -re "\\\[New Thread ${hex} \\\(LWP \[0-9\]+\\\) \\\(id $decimal\\\)\\\].*${gdb_prompt}" {
       pass "${after_new_thread_message}"
     }
-    -re -wrap "\\\[New Thread $decimal\\.$decimal\\\]\r\n.*" {
+    -re -wrap "\\\[New Thread $decimal\\.$decimal\\\ \\\(id $decimal\\\)]\r\n.*" {
       pass $gdb_test_name
     }
   }