public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/29056] New: FAIL: gdb.base/catch-syscall.exp: without arguments: syscall pipe has returned
@ 2022-04-13 5:50 vries at gcc dot gnu.org
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
0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2022-04-13 5:50 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-05-09 10:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-13 5:50 [Bug testsuite/29056] New: FAIL: gdb.base/catch-syscall.exp: without arguments: syscall pipe has returned vries at gcc dot gnu.org
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
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).