[PATCH v2 0/2] [gdb/testsuite] Two gdb.threads patches

[PATCH v2 0/2] [gdb/testsuite] Two gdb.threads patches

[Tom de Vries]

Two patches fixing gdb.threads test-cases.

Changes in v2:
- fix regression noted by Linary CI: use "$srcfile:" prefix when setting
  breakpoints in first patch

Versions:
- v1 https://sourceware.org/pipermail/gdb-patches/2026-July/228901.html

Tom de Vries (2):
  [gdb/testsuite] Fix race in gdb.threads/leader-exit.exp
  [gdb/testsuite] Fix timeout in gdb.threads/vfork-multi-inferior.exp

 gdb/testsuite/gdb.threads/leader-exit.c       |  4 ++++
 gdb/testsuite/gdb.threads/leader-exit.exp     | 24 ++++++++++++++++++-
 gdb/testsuite/gdb.threads/non-ldr-exc-2.c     |  5 ++++
 gdb/testsuite/gdb.threads/non-ldr-exc-2.exp   | 24 ++++++++++++++++++-
 .../gdb.threads/vfork-multi-inferior.exp      |  2 +-
 5 files changed, 56 insertions(+), 3 deletions(-)


base-commit: a238beb05994eec4559abfe65557cc03a2d85645
-- 
2.51.0

[PATCH v2 1/2] [gdb/testsuite] Fix race in gdb.threads/leader-exit.exp

[Tom de Vries]

On aarch64-linux, when running test-case gdb.threads/leader-exit.exp with
"taskset -c 0", 3 out of 10 times I run into:
...
(gdb) continue
Continuing.
[New Thread 0xfffff7d1f160 (LWP 62010) (id 2)]
[Switching to thread 2 (Thread 0xfffff7d1f160 (LWP 62010))]

Thread 2 "leader-exit" hit Breakpoint 2, start (arg=0x0) at leader-exit.c:32
32        sleep (10);  /* break-here */
(gdb) PASS: gdb.threads/leader-exit.exp: continue to breakpoint: break-here
info threads
  Id   Target Id                                                 Frame
  1    Thread 0xfffff7fe8020 (LWP 62008) "leader-exit" (Exiting) \
         0x0000fffff7d46fa0 in __libc_start_call_main () from /lib64/libc.so.6
* 2    Thread 0xfffff7d1f160 (LWP 62010) "leader-exit" \
         start (arg=0x0) at leader-exit.c:32
(gdb) FAIL: gdb.threads/leader-exit.exp: single thread has been left
...

In a passing version, the continue produces a "Thread exited" message, but
that's missing here.

The problem is that after the pthread_join is executed:
...
  i = pthread_join (main_thread, NULL);
  ...

  sleep (10);  /* break-here */
...
there's a race between:
- the breakpoint at break-here triggering, and
- the "Thread exited" message for the main thread being reported.

Fix this by:
- adding a loop before the break location
- waiting in the loop until the "Thread exited" message is seen
- sending ^C to get a prompt
- setting a variable to exit the loop

Likewise in gdb.threads/non-ldr-exc-2.exp.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34425
---
 gdb/testsuite/gdb.threads/leader-exit.c     |  4 ++++
 gdb/testsuite/gdb.threads/leader-exit.exp   | 24 ++++++++++++++++++++-
 gdb/testsuite/gdb.threads/non-ldr-exc-2.c   |  5 +++++
 gdb/testsuite/gdb.threads/non-ldr-exc-2.exp | 24 ++++++++++++++++++++-
 4 files changed, 55 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.threads/leader-exit.c b/gdb/testsuite/gdb.threads/leader-exit.c
index bd546d009cd..b24817e8a14 100644
--- a/gdb/testsuite/gdb.threads/leader-exit.c
+++ b/gdb/testsuite/gdb.threads/leader-exit.c
@@ -21,6 +21,8 @@
 
 static volatile pthread_t main_thread;
 
+static volatile int wait_for_exit = 1;
+
 static void *
 start (void *arg)
 {
@@ -28,6 +30,8 @@ start (void *arg)
 
   i = pthread_join (main_thread, NULL);
   assert (i == 0);
+  while (wait_for_exit)
+    usleep (100 * 1000);
 
   sleep (10);  /* break-here */
   return arg;
diff --git a/gdb/testsuite/gdb.threads/leader-exit.exp b/gdb/testsuite/gdb.threads/leader-exit.exp
index b5e6f558ac7..e53f4cacece 100644
--- a/gdb/testsuite/gdb.threads/leader-exit.exp
+++ b/gdb/testsuite/gdb.threads/leader-exit.exp
@@ -30,7 +30,29 @@ if {![runto_main]} {
     return
 }
 
-gdb_breakpoint [gdb_get_line_number "break-here"]
+# Wait for the "Thread exited" message.
+set re_thread_exited {\[Thread [^\r\n]+ exited\]}
+set saw_thread_exited 0
+gdb_test_multiple "continue" "continue to thread exited" {
+    -re $re_thread_exited {
+	set saw_thread_exited 1
+	# Get a prompt.
+	send_gdb "\003"
+	exp_continue
+    }
+    -re -wrap "" {
+	pass $gdb_test_name
+    }
+}
+gdb_assert {$saw_thread_exited} "thread exited"
+if {!$saw_thread_exited} {
+    return
+}
+
+# Let the inferior to exit the wait_for_exit loop.
+gdb_test_no_output "set var wait_for_exit = 0"
+
+gdb_breakpoint $srcfile:[gdb_get_line_number "break-here"]
 gdb_continue_to_breakpoint "break-here" ".* break-here .*"
 
 gdb_test "info threads" \
diff --git a/gdb/testsuite/gdb.threads/non-ldr-exc-2.c b/gdb/testsuite/gdb.threads/non-ldr-exc-2.c
index b05479be01f..a9e81dfa495 100644
--- a/gdb/testsuite/gdb.threads/non-ldr-exc-2.c
+++ b/gdb/testsuite/gdb.threads/non-ldr-exc-2.c
@@ -26,6 +26,8 @@ static const char *image;
 static volatile pthread_t main_thread;
 static char *argv1 = "go away";
 
+static volatile int wait_for_exit = 1;
+
 static void *
 thread_execler (void *arg)
 {
@@ -34,6 +36,9 @@ thread_execler (void *arg)
   i = pthread_join (main_thread, NULL);
   assert (i == 0);
 
+  while (wait_for_exit)
+    usleep (100 * 1000);
+
   /* Exec ourselves again.  */
   if (execl (image, image, argv1, NULL) == -1) /* break-here */
     {
diff --git a/gdb/testsuite/gdb.threads/non-ldr-exc-2.exp b/gdb/testsuite/gdb.threads/non-ldr-exc-2.exp
index ead262cc2b5..d21ab1d9a56 100644
--- a/gdb/testsuite/gdb.threads/non-ldr-exc-2.exp
+++ b/gdb/testsuite/gdb.threads/non-ldr-exc-2.exp
@@ -37,7 +37,29 @@ proc do_test { lock_sched nonstop } {
 	return -1
     }
 
-    gdb_breakpoint [gdb_get_line_number "break-here"]
+    # Wait for the "Thread exited" message.
+    set re_thread_exited {\[Thread [^\r\n]+ exited\]}
+    set saw_thread_exited 0
+    gdb_test_multiple "continue" "continue to thread exited" {
+	-re $re_thread_exited {
+	    set saw_thread_exited 1
+	    # Get a prompt.
+	    send_gdb "\003"
+	    exp_continue
+	}
+	-re -wrap "" {
+	    pass $gdb_test_name
+	}
+    }
+    gdb_assert {$saw_thread_exited} "thread exited"
+    if {!$saw_thread_exited} {
+	return
+    }
+
+    # Let the inferior to exit the wait_for_exit loop.
+    gdb_test_no_output "set var wait_for_exit = 0"
+
+    gdb_breakpoint $::srcfile:[gdb_get_line_number "break-here"]
     gdb_continue_to_breakpoint "break-here" ".* break-here .*"
 
     if { $nonstop == "on" } {
-- 
2.51.0

[PATCH v2 2/2] [gdb/testsuite] Fix timeout in gdb.threads/vfork-multi-inferior.exp

[Tom de Vries]

With test-case gdb.threads/vfork-multi-inferior.exp I get either:
...
(gdb) run &
Starting program: vfork-multi-inferior-sleep
(gdb) PASS: $exp: method=non-stop: run inferior 2
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) PASS: $exp: method=non-stop: inferior 1
...
or:
...
(gdb) run &
Starting program: vfork-multi-inferior-sleep
(gdb) PASS: $exp: method=non-stop: run inferior 2
inferior 1^M
[Switching to inferior 1 [<null>] (<noexec>)]^M
(gdb) PASS: $exp: method=non-stop: inferior 1
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib64/libthread_db.so.1".^M
...

With a 16.3-based package on aarch64-linux, I ran into:
...
(gdb) run &
Starting program: vfork-multi-inferior-sleep
(gdb) PASS: $exp: method=non-stop: run inferior 2
inferior 1
[Switching to inferior 1 [<null>] (<noexec>)]
(gdb) [Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
FAIL: $exp: method=non-stop: inferior 1
(timeout)
...

Unfortunately I have not been able to reproduce this.

Fix this using -no-prompt-anchor.

See also commit 5f69c00a6e0 ("[gdb/testsuite] Fix timeout in
gdb.base/async-shell.exp").

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34427
---
 gdb/testsuite/gdb.threads/vfork-multi-inferior.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.threads/vfork-multi-inferior.exp b/gdb/testsuite/gdb.threads/vfork-multi-inferior.exp
index e258ec719e9..f6c90bf0655 100644
--- a/gdb/testsuite/gdb.threads/vfork-multi-inferior.exp
+++ b/gdb/testsuite/gdb.threads/vfork-multi-inferior.exp
@@ -86,7 +86,7 @@ proc do_test {method} {
     }
 
     # Start the first inferior.
-    gdb_test "inferior 1" "Switching to inferior 1 .*"
+    gdb_test -no-prompt-anchor "inferior 1" "Switching to inferior 1 .*"
     gdb_file_cmd ${::binfile}
     gdb_test "break should_break_here" "Breakpoint $::decimal at .*"
     gdb_test "start" "Thread 1.1 .* hit Temporary breakpoint.*" \
-- 
2.51.0

Re: [PATCH v2 0/2] [gdb/testsuite] Two gdb.threads patches

[Kevin Buettner]

Hi Tom,

On Fri, 24 Jul 2026 04:44:25 +0200
Tom de Vries <tdevries@suse.de> wrote:

> Two patches fixing gdb.threads test-cases.
> 
> Changes in v2:
> - fix regression noted by Linary CI: use "$srcfile:" prefix when setting
>   breakpoints in first patch
> 
> Versions:
> - v1 https://sourceware.org/pipermail/gdb-patches/2026-July/228901.html
> 

Both patches LGTM.

Approved-By: Kevin Buettner <kevinb@redhat.com>