From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ACB9338582B7; Thu, 4 Jan 2024 11:20:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ACB9338582B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704367245; bh=mEIJ3AG0IGAcDfaI8Yx9xOnso5HQtqHkX/IiSc/Lg+g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uBeyFbbrG9Mx/y/iKRUJlw8EBT5CeMqbDALvyoZjlEii7IPDB44WB4rq3z9lISNIR mWqD2yHtGyzxqmeG9GVieRXxC1CqpFSoRo2xe9rgugK2XEB2Dfl+GHZ+czyoSVqmAg gqLZpcaJEZfpSbqMpWKKy8smnC8Kp/wjFkwddjjQ= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/31203] [gdb] FAIL: gdb.base/kill-during-detach.exp: exit_p=true: checkpoint_p=true: python kill_and_detach() Date: Thu, 04 Jan 2024 11:20:44 +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=3D31203 --- Comment #8 from Tom de Vries --- (In reply to Kevin Buettner from comment #7) > Thus far, I haven't been able to reproduce it. I started from a clean os install, built and tested gdb, and then used grep= ping UNTESTED/UNSUPPORTED to add packages and configure settings to make the bui= ld more complete. At some point in this process I started running into this failure. So I decided to revert this process, but didn't manage, a very minimal gdb still reproduced the failure 100% of the time. I also did some updates at some point, so I was in the 'need restart' state= .=20 After restarting, the failure disappeared. I investigated the file descriptor list in /proc//fd, and found two sockets where I previously found the files mentioned in comment 6. Anyway, I wrote a patch for the test-case that allows us reproduce the fail= ure reliably, also on x86-64-linux. --=20 You are receiving this mail because: You are on the CC list for the bug.=