public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/29252] New: [gdb/testsuite] FAIL: gdb.threads/tid-reuse.exp: continue to breakpoint: after_reuse_time
@ 2022-06-16 7:42 vries at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: vries at gcc dot gnu.org @ 2022-06-16 7:42 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29252
Bug ID: 29252
Summary: [gdb/testsuite] FAIL: gdb.threads/tid-reuse.exp:
continue to breakpoint: after_reuse_time
Product: gdb
Version: 12.1
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With gdb 12.1, in OBS for openSUSE Leap_15.2 x86_64 I ran into:
...
(gdb) break after_reuse_time^M
Breakpoint 4 at 0x555555554b84: file
/home/abuild/rpmbuild/BUILD/gdb-12.1/gdb/testsuite/gdb.threads/tid-reuse.c,
line 95.^M
(gdb) continue^M
Continuing.^M
^M
Program terminated with signal SIGKILL, Killed.^M
The program no longer exists.^M
(gdb) FAIL: gdb.threads/tid-reuse.exp: continue to breakpoint: after_reuse_time
...
I'm not sure where this KILL is coming from.
The testsuite is run like this:
...
./orphanripper make -j16 -k check//unix/-m64 check//unix/-m64/-fno-PIE/-no-pie
check//unix/-m32 check//unix/-m32/-fno-PIE/-no-pie
...
so maybe it's a problem with the orphanripper, maybe it's a problem with a
stray kill from another test-case run in parallel.
For now classifying as testsuite problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-06-16 7:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-16 7:42 [Bug testsuite/29252] New: [gdb/testsuite] FAIL: gdb.threads/tid-reuse.exp: continue to breakpoint: after_reuse_time 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).