[binutils-gdb] Fix multiple-successive-infcall.exp with gdbserver

Tom Tromey tromey@sourceware.org
Sun Jan 18 15:33:50 GMT 2026


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=83bf604ebf1d271b069947d48e291347e168c52c

commit 83bf604ebf1d271b069947d48e291347e168c52c
Author: Tom Tromey <tom@tromey.com>
Date:   Sat Jan 17 19:28:13 2026 -0700

    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:
---
 gdb/testsuite/gdb.threads/multiple-successive-infcall.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp b/gdb/testsuite/gdb.threads/multiple-successive-infcall.exp
index ae3bcee0bee..732793010ef 100644
--- 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
     }
   }


More information about the Gdb-cvs mailing list