public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cel at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31312] New: attach-many-short-lived-threads gives inconsistent results Date: Mon, 29 Jan 2024 18:06:40 +0000 [thread overview] Message-ID: <bug-31312-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31312 Bug ID: 31312 Summary: attach-many-short-lived-threads gives inconsistent results Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: cel at linux dot ibm.com Target Milestone: --- Created attachment 15340 --> https://sourceware.org/bugzilla/attachment.cgi?id=15340&action=edit run 1, Power 10 gdb.log for the attach-many-short-lived-thread The test when run on Power gives inconsistent results. It seems like the Power 10 system running: Fedora Linux 38 (Server Edition) GNU gdb (GDB) 15.0.50.20240126-git gcc (GCC) 13.2.1 20231011 (Red Hat 13.2.1-4) seem to be more unstable then the Power 9 system where the gdb daily builds are run. I have attached the gdb/testsuite/gdb.log file for the test run with the command: make check RUNTESTFLAGS='GDB=/home/carll/bin/gdb gdb.threads/attach-many-short-lived-threads.exp ' -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-29 18:06 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 18:06 cel at linux dot ibm.com [this message] 2024-01-29 18:08 ` [Bug testsuite/31312] " cel at linux dot ibm.com 2024-01-29 18:20 ` tromey at sourceware dot org 2024-01-29 20:55 ` vries at gcc dot gnu.org 2024-01-29 21:35 ` cel at linux dot ibm.com 2024-01-29 21:44 ` cel at linux dot ibm.com 2024-01-29 22:38 ` cel at linux dot ibm.com 2024-01-30 7:21 ` vries at gcc dot gnu.org 2024-01-30 10:13 ` vries at gcc dot gnu.org 2024-01-31 16:14 ` cel at linux dot ibm.com 2024-02-06 18:59 ` cel at linux dot ibm.com 2024-02-12 18:58 ` tromey at sourceware dot org 2024-02-12 18:59 ` tromey at sourceware dot org 2024-02-16 4:42 ` cel at linux dot ibm.com 2024-03-09 0:45 ` tromey at sourceware dot org 2024-03-09 1:29 ` cel at linux dot ibm.com 2024-03-09 6:59 ` brobecker at gnat dot com 2024-03-09 16:43 ` tromey at sourceware dot org 2024-03-15 16:41 ` cel at linux dot ibm.com 2024-03-15 21:57 ` thiago.bauermann at linaro dot org 2024-03-16 1:37 ` thiago.bauermann at linaro dot org 2024-03-16 17:42 ` tromey at sourceware dot org 2024-03-18 18:45 ` thiago.bauermann at linaro dot org 2024-03-19 15:14 ` cel at linux dot ibm.com 2024-03-19 15:35 ` thiago.bauermann at linaro dot org 2024-03-19 15:57 ` cel at linux dot ibm.com 2024-03-19 19:10 ` thiago.bauermann at linaro dot org 2024-03-21 23:17 ` thiago.bauermann at linaro dot org 2024-04-14 17:56 ` brobecker at gnat dot com 2024-04-16 4:56 ` thiago.bauermann at linaro dot org 2024-04-17 14:52 ` pedro at palves dot net 2024-04-30 2:37 ` cvs-commit at gcc dot gnu.org 2024-05-10 22:14 ` brobecker at gnat dot com 2024-05-10 22:28 ` cel at linux dot ibm.com 2024-05-11 23:48 ` thiago.bauermann at linaro dot org 2024-05-13 19:03 ` tromey at sourceware dot org 2024-05-14 15:24 ` cel at linux dot ibm.com 2024-05-17 16:26 ` tromey at sourceware dot org 2024-05-17 16:33 ` cel at linux dot ibm.com 2024-05-17 17:10 ` vries at gcc dot gnu.org 2024-05-17 19:54 ` cel at linux dot ibm.com 2024-05-17 19:58 ` pedro at palves dot net 2024-05-17 23:02 ` cel at linux dot ibm.com
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-31312-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).