With a 13.2 based package I run into: ... (gdb) PASS: gdb.base/vfork-follow-parent.exp: resolution_method=schedule-multiple: continue to end of inferior 2 inferior 1^M [Switching to inferior 1 [process 24968] (/home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m64.-fno-PIE.-no-pie/outputs/gdb.base/vfork-follow-parent/vfork-follow-parent)]^M [Switching to thread 1.1 (Thread 0x7ffff7fbbb80 (LWP 24968))]^M #0 0x00007ffff7cda937 in clock_nanosleep@GLIBC_2.2.5 () from /lib64/libc.so.6^M (gdb) Reading symbols from /home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m64.-fno-PIE.-no-pie/outputs/gdb.base/vfork-follow-parent/vfork-follow-parent...^M FAIL: gdb.base/vfork-follow-parent.exp: resolution_method=schedule-multiple: inferior 1 (timeout) ... I suppose this could be fixed by using -no-prompt-anchor on: ... gdb_test "inferior 1" ".*Switching to inferior 1.*" ... I have not been able to reproduce this outside of OBS yet.
(In reply to Tom de Vries from comment #0) > I have not been able to reproduce this outside of OBS yet. Managed to reproduce using taskset -c 0: ... FAIL: gdb.base/vfork-follow-parent.exp: exec_file=vfork-follow-parent-exit: target-non-stop=on: non-stop=off: resolution_method=schedule-multiple: inferior 1 (timeout) FAIL: gdb.base/vfork-follow-parent.exp: exec_file=vfork-follow-parent-exit: target-non-stop=off: non-stop=off: resolution_method=schedule-multiple: inferior 1 (timeout) ...
The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6ccc6caf4906036f8d5778fd5a412a199621745e commit 6ccc6caf4906036f8d5778fd5a412a199621745e Author: Tom de Vries <tdevries@suse.de> Date: Mon Jan 8 13:01:50 2024 +0100 [gdb/testsuite] Add missing -no-prompt-anchor in gdb.base/vfork-follow-parent.exp When running test-case gdb.base/vfork-follow-parent.exp it passes fine, but when running it with "taskset -c 0" I run into: ... (gdb) inferior 1^M [Switching to inferior 1 [process 26606] (vfork-follow-parent-exit)]^M [Switching to thread 1.1 (process 26606)]^M (gdb) Reading symbols from vfork-follow-parent-exit...^M FAIL: $exp: exec_file=vfork-follow-parent-exit: target-non-stop=on: \ non-stop=off: resolution_method=schedule-multiple: inferior 1 (timeout) ... Fix this by using -no-prompt-anchor. Tested on x86_64-linux. PR testsuite/31166 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31166
Fixed.