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/29252] New: [gdb/testsuite] FAIL: gdb.threads/tid-reuse.exp: continue to breakpoint: after_reuse_time Date: Thu, 16 Jun 2022 07:42:01 +0000 [thread overview] Message-ID: <bug-29252-4717@http.sourceware.org/bugzilla/> (raw) 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.
reply other threads:[~2022-06-16 7:42 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-29252-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: linkBe 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).