public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31166] New: [gdb/testsuite] FAIL: gdb.base/vfork-follow-parent.exp: resolution_method=schedule-multiple: inferior 1 (timeout)
Date: Thu, 14 Dec 2023 08:52:09 +0000	[thread overview]
Message-ID: <bug-31166-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31166

            Bug ID: 31166
           Summary: [gdb/testsuite] FAIL:
                    gdb.base/vfork-follow-parent.exp:
                    resolution_method=schedule-multiple: inferior 1
                    (timeout)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-12-14  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  8:52 vries at gcc dot gnu.org [this message]
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
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@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: link
Be 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).