public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29821] New: native-gdbserver: FAIL: gdb.base/vfork-follow-parent.exp: resolution_method=schedule-multiple: continue to break_parent
Date: Wed, 23 Nov 2022 01:46:42 +0000	[thread overview]
Message-ID: <bug-29821-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29821
           Summary: native-gdbserver: FAIL:
                    gdb.base/vfork-follow-parent.exp:
                    resolution_method=schedule-multiple: continue to
                    break_parent
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

I got this once on my CI.

 879931 (gdb) continue^M
 879932 Continuing.^M
 879933 ^M
 879934 Breakpoint 1, main () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.base/vfork-follow-parent.c:30^M
 879935 30        alarm (30);^M
 879936 (gdb) break break_parent^M
 879937 Breakpoint 2 at 0x5555555551b1: file
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.base/vfork-follow-parent.c,
line 25.^M
 879938 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: break break_parent
 879939 continue^M
 879940 Continuing.^M
 879941 Can not resume the parent process over vfork in the foreground while^M
 879942 holding the child stopped.  Try "set detach-on-fork" or "set
schedule-multiple".^M
 879943 0x00007ffff7e76c3c in vfork () from /lib/x86_64-linux-gnu/libc.so.6^M
 879944 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: continue to vfork
 879945 continue^M
 879946 Continuing.^M
 879947 Can not resume the parent process over vfork in the foreground while^M
 879948 holding the child stopped.  Try "set detach-on-fork" or "set
schedule-multiple".^M
 879949 0x00007ffff7e76c3c in vfork () from /lib/x86_64-linux-gnu/libc.so.6^M
 879950 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: try to continue from vfork
 879951 set schedule-multiple on^M
 879952 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: set schedule-multiple on
 879953 continue^M
 879954 Continuing.^M
 879955 [New inferior 2 (process 970302)]^M
 879956 [Inferior 2 (process 970302) exited normally]^M
 879957 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: continue to end of inferior 2
 879958 inferior 1^M
 879959 [Switching to inferior 1 [process 970290]
(/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-gdbserver/tmp/tmp.5bGk6ccCMD/gdb/testsuite/outputs/gdb.base/vfork-follow-parent/vfo
       rk-follow-parent)]^M
 879960 [Switching to thread 1.1 (Thread 970290.970290)]^M
 879961 #0  <unavailable> in ?? ()^M
 879962 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: inferior 1
 879963 print unblock_parent = 1^M
 879964 $1 = 1^M
 879965 (gdb) PASS: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: print unblock_parent = 1
 879966 continue^M
 879967 Continuing.^M
 879968 PC register is not available^M
 879969 (gdb) FAIL: gdb.base/vfork-follow-parent.exp:
resolution_method=schedule-multiple: continue to break_parent

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

                 reply	other threads:[~2022-11-23  1:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-29821-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).