public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31166] [gdb/testsuite] FAIL: gdb.base/vfork-follow-parent.exp: resolution_method=schedule-multiple: inferior 1 (timeout) Date: Mon, 08 Jan 2024 12:01:24 +0000 [thread overview] Message-ID: <bug-31166-4717-noTapBQdxs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31166-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31166 --- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-08 12:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-14 8:52 [Bug testsuite/31166] New: " vries at gcc dot gnu.org 2023-12-14 8:52 ` [Bug testsuite/31166] " vries at gcc dot gnu.org 2024-01-08 10:47 ` vries at gcc dot gnu.org 2024-01-08 12:01 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-08 12:02 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31166-4717-noTapBQdxs@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).