From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 098923858CDA; Wed, 2 Aug 2023 00:35:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 098923858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1690936522; bh=gAft2/LJHWDTWTsVzNTjF4cfawlzX3i2p98F6ON8e+g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=g7c8Ai18KS0Ih0aWeE0aUDdBhf3/ZBjoGvZTxsHYUEs6yRyntkUjMLvk3eU0mUphl zyNnvx1E62EiJB4Bh2E5yBSACCinLGnpUBv7oCl+fbA9DjAJTiFP5NBRdIqy5pSj5Q 1uN7ktL0fejjWjcVid0I5H3QZE1mSxTnB1aAlhrM= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30695] [gdb, tsan] FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution Date: Wed, 02 Aug 2023 00:35:15 +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=3D30695 --- Comment #2 from Tom de Vries --- >From https://www.gnu.org/software/libc/manual/html_node/Merged-Signals.html: ... If multiple signals of the same type are delivered to your process before y= our signal handler has a chance to be invoked at all, the handler may only be invoked once, as if only a single signal had arrived. In effect, the signals merge into one. This situation can arise when the signal is blocked, or in a multiprocessing environment where the system is busy running some other processes while the signals are delivered. This means, for example, that you cannot reliably use a signal handler to count signals. The only distinction= you can reliably make is whether at least one signal has arrived since a given = time in the past.=20 ... --=20 You are receiving this mail because: You are on the CC list for the bug.=