DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 4AMLC3fd498610
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 4AMLC3fd498610
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=IrwyjXR1
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org CC3A33858408
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1732309921;
	bh=kZXL3FyZedOasSriRDH3LCC5TN0dJLGYOqMq6PpcCt4=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=IrwyjXR1u3bWcmeuvBpnEVJvCwltZp8JFXSvKYL5LxWWGSqb/nPuL6ke5QuVe2DVF
	Aj0Ppbdxh57k6UjNbBc0m8K24x6mvJqz3Aj6U4pBPdeVQ94ZJDWFf0zhUIRUji29Zn
	h5ZXz0UCWH+TJg8e/LPhLMpieW36spiF+/bXdGJU=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 12BFC3858D20
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 12BFC3858D20
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1732309858; cv=none;
	b=xWuiPr4uPEnlqVgUE9gRntoMMxH5Qobkr9QD/bG5AjsrAdUPqUzpStb6kQHYi2QxWE1ZS8dW9dYfB1KEkTwG2gS9aBns3vQz3vc/jOo89aigsimnOJmfItCLSm1UXDBPVIpQs/MDJNPU9IPG3eD6uBD3GosyU22aY+4K7Cz9Kas=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1732309858; c=relaxed/simple;
	bh=emRLVO0146qDRFqyTe+qbMA5S+GatFLlZzgfRuaH5xs=;
	h=Message-ID:Date:MIME-Version:Subject:To:From:DKIM-Signature;
	b=YcT5PyxZGY+pn3aAl13gKXgTfQWzOuIWWEkuR7/KMt5yHQOuA4+pMgPDU9hMdfPvdxGuA5KsBvbHKvV9A8SFzIUSkBbSdZ3D6dNG+VTGFeP1k5DO3jqWlAYfcpRewT47P8wr/7r9GixD2qteE0d+8Y496zqjy6GdYAyGDYJCLuU=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 12BFC3858D20
Message-ID:	<03b4e46b-5ea8-4414-8ca3-950defad9828@SystematicSW.ab.ca>
Date:	Fri, 22 Nov 2024 14:10:55 -0700
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
Subject:	Re: Signals may be lost during setjmp or longjmp
To:	cygwin AT cygwin DOT com
References:	<d36f374f-8352-2f0f-c8ae-be20ad7c49a7 AT t-online DOT de>
Organization:	Systematic Software
In-Reply-To:	<d36f374f-8352-2f0f-c8ae-be20ad7c49a7@t-online.de>
X-Rspamd-Queue-Id:	2D2162000D
X-Rspamd-Server:	rspamout01
X-Stat-Signature:	g6u8y1qpumybxwhuqs4wp1h1txzjnfhm
X-Session-Marker:	427269616E2E496E676C69734053797374656D6174696353572E61622E6361
X-Session-ID:	U2FsdGVkX19SW82P9GuiuGMJCo4DkXh/uXDK7wUrDOE=
X-HE-Tag:	1732309841-878039
X-HE-Meta:	U2FsdGVkX19M8FfV1XIAtoF/LjWN4rfdWgOZY3Nydv1NwrzCQ+h0TaOcSlcfpOuvg2/nDBlvAXpqestn6EXWKVyXwR/k9B1kZQBP2HuDBAzUz7Zkna0BczDtabJnb3J9kC9Ulz66aJoNcMJWnpy7Qqal0tTwZivtMmFk7iMy3qu7DFbVIeWIBgEYgHfJ/SYLZ0HhkboyRos/gT9JA2fwQrCSVPv1ObXUuum386aeTgn+qxUIFc4fvXt70jAsuEsALRtjydjTVXVOIlCf66h59RCTlJaDYoCTEPEwfWKcyzgXuVlE9DtAg/cCgg3ZF3B2wjTQj6DIhSwV/1PzGk6+T+Nwp+64ia1F
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Brian Inglis <Brian DOT Inglis AT SystematicSW DOT ab DOT ca>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 4AMLC3fd498610

On 2024-11-22 07:22, Christian Franke via Cygwin wrote:
> The command 'stress-ng --longjmp ... -t 1' occasionally fails to terminate 
> because some child process does not receive the SIGALRM indicating timeout.
> 
> Testcase (attached):
> 
> $ g++ -O2 -o longjmpsigs longjmpsigs.cc
> 
> $ ./longjmpsigs
> [^C]
> INT   1
> [^C]
> INT   2
> ...
> [^C]
> INT   21
> [^C]
> [^C]
> INT   22
> ...
> 
> The following run in a second window may not stop the process due to few lost 
> signals:
> 
> for i in {1..100}; do
>    echo $i; killall -INT longjmpsigs || break; sleep 1
> done
> 
> The problem does not occur if a regular loop is used instead of setjmp/longjmp.
> 
> Reproducible also with current cygwin1.dll 26144e40.

I have some cygport package build tests which hang and need killed despite them 
using usual test harnesses setting timeouts, typically running ~100% all CPUs!

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -