From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7691B3858C98; Sat, 16 Mar 2024 17:42:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7691B3858C98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710610951; bh=mLN5XsH0cjcziuVuxZ409nJ6mKqbDjj45nr0UrfHBsM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JbB4tWdDHmbFnfpjbKueY044SBvqYNx9BfFVU7SAm9GIvydHnHFBRYdvmnledORAq SgcUYPyb0pX2L8wP+mA1B91Z+V/UfBXPbJP8dTPx0OFlc9sB1MLUKzwSEcOCIJnovp ppJukcHM9ZYP1Vl5tybBkXT38aVnJHz1OFAXIjg8= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31312] attach-many-short-lived-threads gives inconsistent results Date: Sat, 16 Mar 2024 17:42:30 +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: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: 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 --- Comment #18 from Tom Tromey --- > The gdb log says that it detached from the pid. I don't find any way to = verify that. I don't see any gdb attached thread status command that would= verify it.=20=20 Yeah, what I would suggest is maybe modifying the test case to invoke 'strace gdb ..' with some options to log the strace output to a file; then examine the file to see if gdb correctly detaches from all the threads it attached to. That is, I'm wondering if there's some underlying bug that we haven't properly recognized -- this would account for the weirdness where one failed attach leaves gdb unable to attach in the future. Thiago's experiments here seem to indicate this could be the case. If we are really convinced there is a kernel bug then I think re-trying the test is not so important. On the first failure it can just bail out. --=20 You are receiving this mail because: You are on the CC list for the bug.=