public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot 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: Fri, 07 Jun 2024 00:13:20 +0000 [thread overview] Message-ID: <bug-31832-4717-E52omUVReF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31832-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31832 Thiago Jung Bauermann <thiago.bauermann at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thiago.bauermann at linaro dot org --- Comment #5 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> --- In bug #31312, the testcase timed out because when there was one or more zombie threads in the inferior, it would enter an infinite loop while processing all new threads because at each iteration it thought that the zombie threads were new. Because of the infinite loop, the GDB prompt would never show up in gdb.log. In this case, the testcase times out during attach but eventually the GDB prompt appears and GDB seems to work. Apparently the attach process just takes a long time. I haven't seen this behaviour when I was investigating bug #31312. I don't understand what could cause attach to take so long but still complete. The only thing I can think of is that perhaps find() and insert() operations in the visited_lwps std::unordered_set added by commit c930a077225e ("gdb/nat/linux: Fix attaching to process when it has zombie threads") are taking too long? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-07 0:13 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 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 [this message] 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-E52omUVReF@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).