From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C73FD3858C50; Fri, 28 Jul 2023 16:04:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C73FD3858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1690560278; bh=Xi2Cv1ETeC1yrBUSjnligCwD7CI7LSntV0+jzvcL3Yg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZeH/JjynAa7auRmZUOrK+rwy9wbVwgJfqzZ2nYBajSpmAAaAgBWkEhbSWc0SdBnwT 5iwwmmyDhb8k17W2lh1X0x0KuQQaAlWy3Bfkiy7AmIg0jWDRS+YLUSPIo70a96XDua VSQHWyOJW91JWbBEuPYQSmfFfq+jDglHi+yrYnh8= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug dap/30680] [gdb/dap] ThreadSanitizer: data race gdbsupport/event-pipe.h:44 in event_pipe::is_open() const Date: Fri, 28 Jul 2023 16:04:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: dap X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot 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=3D30680 --- Comment #10 from Tom Tromey --- I definitely (but intermittently) see the failure with the assert patch applied. I'm not much closer to finding the problem, though. I think the challenge is finding out what bit of code might be unblocking SIGCHLD on this thread. --=20 You are receiving this mail because: You are on the CC list for the bug.=