From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D54AB3865C11; Wed, 22 May 2024 09:48:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D54AB3865C11 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1716371311; bh=y+v4fIpy77yq0D8BaeXR09nn7eb3AUGwyVL0uuhu3ls=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xkhWEB1iQR6knKXxhI2VAv2//YQD89RyN3rPlGTxS/pqoKDjb9+vcetyRHOX01rl/ gYVFA85mf2ZGiOjfJ6sf6HgRY4VyRSaCrtEioKhaLcZYOW3xrouzKMK0VN+FnXspWS yj+h2ZM7vNplwS840DIWKAEhqIebxF9AnhFWgMc8= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31312] attach-many-short-lived-threads gives inconsistent results Date: Wed, 22 May 2024 09:48:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: cel at linux dot ibm.com X-Bugzilla-Target-Milestone: 15.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31312 Tom de Vries changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #41 from Tom de Vries --- (In reply to Thiago Jung Bauermann from comment #40) > So if one accepts my suggestion of using this PR to track the problem of = GDB > entering an infinite loop in the presence of zombie inferior threads, then > based on the gdb.sum that Carl posted I'd argue that there's no evidence > that it's still happening. Agreed. Just to recap briefly, comment 19 mentions three problems observed in the test-case, which are handled in three different PRs. Problem 1. This PR. Problem 2. PR 31512 - gdb.threads/attach-many-short-lived-threads.exp sometimes fails with "process 2689792 is already traced by process 2039527". Problem 3. PR 26286 - FAIL: gdb.threads/attach-many-short-lived-threads.ex= p: iter 1: break at break_fn: 1 (SIGTRAP). This PR was closed after committing a fix for problem 1. It was reopened d= ue to observing FAILs in the test-case, but atm there's no evidence that probl= em 1 in fact re-emerged. It could be one of the other two problems, or even yet another problem. Re-closing until there is evidence that problem 1 re-emerged. --=20 You are receiving this mail because: You are on the CC list for the bug.=