From: Tom de Vries <tdevries@suse.de>
Date: Mon, 8 Jan 2024 12:01:50 +0000 (+0100)
Subject: [gdb/testsuite] Add missing -no-prompt-anchor in gdb.base/vfork-follow-parent.exp
X-Git-Tag: upstream/2.42~213
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6ccc6caf4906036f8d5778fd5a412a199621745e;p=platform%2Fupstream%2Fbinutils.git

[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
---

diff --git a/gdb/testsuite/gdb.base/vfork-follow-parent.exp b/gdb/testsuite/gdb.base/vfork-follow-parent.exp
index a29706f..85446df 100644
--- a/gdb/testsuite/gdb.base/vfork-follow-parent.exp
+++ b/gdb/testsuite/gdb.base/vfork-follow-parent.exp
@@ -92,7 +92,7 @@ proc do_test { exec_file resolution_method target_non_stop non_stop } {
 	gdb_test "set schedule-multiple on"
 	gdb_test "continue" "$::inferior_exited_re normally.*" \
 	    "continue to end of inferior 2"
-	gdb_test "inferior 1" ".*Switching to inferior 1.*"
+	gdb_test -no-prompt-anchor "inferior 1" ".*Switching to inferior 1.*"
 	gdb_test "print unblock_parent = 1" " = 1"
     } else {
 	error "invalid resolution method: $resolution_method"