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 gdb/31832] [gdb] FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 3: attach (timeout) Date: Sat, 01 Jun 2024 08:10:51 +0000 [thread overview] Message-ID: <bug-31832-4717-o05TeKfsQb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31832-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31832 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- I reran the test-case, and got: ... (gdb) builtin_spawn /home/vries/gdb/build/gdb/testsuite/outputs/gdb.threads/attach-many-short-lived-threads/attach-many-short-lived-threads^M attach 416753^M Attaching to program: /home/vries/gdb/build/gdb/testsuite/outputs/gdb.threads/attach-many-short-lived-threads/attach-many-short-lived-threads, process 416753^M FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: attach (timeout) info threads^M Cannot attach to lwp 1620134: Operation not permitted (1)^M (gdb) info threads^M ... So, this is reproducible. In this case the timeout happens at the initial attach, that may be relevant information. For context, this is on a machine with 192 cores, and when starting the test-case the load is somewhere below 10. In the course of running the test-case this gradually climbs to 130, but it doesn't look like the timeout is caused by system load, given that it's low to start with. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-01 8:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-01 7:17 [Bug gdb/31832] New: " vries at gcc dot gnu.org 2024-06-01 7:23 ` [Bug gdb/31832] " vries at gcc dot gnu.org 2024-06-01 8:10 ` vries at gcc dot gnu.org [this message] 2024-06-02 12:36 ` bernd.edlinger at hotmail dot de 2024-06-03 16:58 ` vries at gcc dot gnu.org 2024-06-07 0:13 ` thiago.bauermann at linaro dot org 2024-06-12 9:53 ` vries at gcc dot gnu.org 2024-06-21 1:21 ` thiago.bauermann at linaro dot org 2024-06-21 10:18 ` 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-31832-4717-o05TeKfsQb@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).