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/29056] New: FAIL: gdb.base/catch-syscall.exp: without arguments: syscall pipe has returned
Date: Wed, 13 Apr 2022 05:50:44 +0000	[thread overview]
Message-ID: <bug-29056-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29056
           Summary: FAIL: gdb.base/catch-syscall.exp: without arguments:
                    syscall pipe has returned
           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: ---

On openSUSE Tumbleweed, there's a cluster of FAILs related to pipe system call
in this test-case:
...
FAIL: gdb.base/catch-syscall.exp: without arguments: syscall pipe has returned
FAIL: gdb.base/catch-syscall.exp: with many arguments: program has called pipe
FAIL: gdb.base/catch-syscall.exp: with many arguments: syscall pipe has
returned
FAIL: gdb.base/catch-syscall.exp: with many arguments: program has called write
FAIL: gdb.base/catch-syscall.exp: with many arguments: syscall write has
returned
FAIL: gdb.base/catch-syscall.exp: with many arguments: program has called read
(the program exited)
FAIL: gdb.base/catch-syscall.exp: with many arguments: syscall read has
returned (the program is no longer running)
FAIL: gdb.base/catch-syscall.exp: with many arguments: continue until exit (the
program is no longer running)
FAIL: gdb.base/catch-syscall.exp: without args noxml: pipe: program has called
22
FAIL: gdb.base/catch-syscall.exp: without args noxml: pipe: syscall 22 has
returned
FAIL: gdb.base/catch-syscall.exp: with args noxml: program has called 22
FAIL: gdb.base/catch-syscall.exp: with args noxml: syscall 22 has returned
FAIL: gdb.base/catch-syscall.exp: with args noxml: program has called 1
FAIL: gdb.base/catch-syscall.exp: with args noxml: syscall 1 has returned
FAIL: gdb.base/catch-syscall.exp: with args noxml: program has called 0 (the
program exited)
FAIL: gdb.base/catch-syscall.exp: with args noxml: syscall 0 has returned (the
program is no longer running)
...

And these look related:
...
FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2
FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2
...

First in more detail:
...
(gdb) PASS: gdb.base/catch-syscall.exp: without arguments: program has called
pipe
continue^M
Continuing.^M
^M
Catchpoint 2 (returned from syscall pipe2), 0x00007ffff7daabdd in pipe () from
/lib64/libc.so.6^M
(gdb) FAIL: gdb.base/catch-syscall.exp: without arguments: syscall pipe has
returned
...

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

             reply	other threads:[~2022-04-13  5:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  5:50 vries at gcc dot gnu.org [this message]
2022-05-03 15:00 ` [Bug testsuite/29056] " vries at gcc dot gnu.org
2022-05-09 10:46 ` [Bug gdb/29056] " 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-29056-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).