From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 929183875DC6; Sat, 1 Jun 2024 08:10:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 929183875DC6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1717229452; bh=psbegtft2KyudQ05OrWwymS4TpG5RV9pMRmoqdUgFFI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=noESOig5QKIxBN0anT8hmSn7B4NaeZ/QPVEznZaTn7rfaujWQ8aORyIRDkEz5fjiA TAWE6Tg/REXEbYFL+xLI4kJypT38uX0+z86ohx+F/5lMwy45Tah5vqI3LpjHtj8aUk 1I15mG8e6exAw5Ch0jpZMNSfo5eLQ45y2YedPkwA= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- 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=3D31832 --- Comment #2 from Tom de Vries --- I reran the test-case, and got: ... (gdb) builtin_spawn /home/vries/gdb/build/gdb/testsuite/outputs/gdb.threads/attach-many-short-l= ived-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-l= ived-threads/attach-many-short-lived-threads, process 416753^M FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: attach (time= out) 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 timeou= t is caused by system load, given that it's low to start with. --=20 You are receiving this mail because: You are on the CC list for the bug.=