From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id BCC5F3858422; Mon, 31 Jul 2023 12:37:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BCC5F3858422
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1690807024;
	bh=QwoHC6oL+XR+n1YWyJh4rycQnBZVEeZXV0sKem5NfZc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=nOYLVAFiz+iHn6gntG2Q9xIts28O8Dhzqikr+9GC5KxGtovztSnUBQ0nm17sxEwGp
	 jb4dbUs7XTyvkf2QBYeJfHcgVyLreVlQLZYiwfBpvafBkh8Vq+qwixRr/WkQvZfBI8
	 +39RhVAAz1DIzv6BE+yRESsvx7RIv/p/Y15la6p4=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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: Mon, 31 Jul 2023 12:37:03 +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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 14.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30680-4717-rpIZvWpUY1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30680-4717@http.sourceware.org/bugzilla/>
References: <bug-30680-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30680

--- Comment #14 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot g=
nu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D30c01bb104e4=
dfc50e8cf3d0312bbf7d22f73d10

commit 30c01bb104e4dfc50e8cf3d0312bbf7d22f73d10
Author: Tom Tromey <tromey@adacore.com>
Date:   Fri Jul 28 12:02:38 2023 -0600

    Restore previous sigmask in gdb.block_signals

    Tom de Vries found a bug where, sometimes, a SIGCHLD would be
    delivered to a non-main thread, wreaking havoc.

    The problem is that gdb.block_signals after first blocking a set of
    signals, then unblocked the same set rather than restoring the initial
    situation.  This function being called from the DAP thread lead to
    SIGCHLD being unblocked there.

    This patch fixes the problem by restoring the previous set of signals
    instead.

    Tested-by: Tom de Vries <tdevries@suse.de>
    Reviewed-By: Tom de Vries <tdevries@suse.de>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30680

--=20
You are receiving this mail because:
You are on the CC list for the bug.=