X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=x3QIi7vrt1DtGxwXz2klnB12p6ZjC+Eod+nuS8io+VCxmQ00DixmV
	AXRtp9pFii3D/c2JXIKo6U/k8e4Awj3AS8XGHngJze8DFq8u250rjzF5DX0bpZUI
	KWBOUa+awldvhCMkWnRTF77XIRK9KA5Sjd1jwoFfhQr1QMGFayC35c=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=LP2c9R0OHfr839wwqWQ0BqYafx4=; b=iIiVHk3QiJb4alDo05TZaOLtjmKt
	OPKC2laf+YD0/qI2MEjEzk1w5QwPyoOW1wTklHH/e00+4DtmNXbET5/wunVHbLzO
	7+2GcjElvoMwrIUJOcSwtNbdQO+TdrxcWCye8m3NpvC/mlO3Vfo1r2za1rrdKfc0
	xYN9+makfwfrrHM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-100.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=
X-HELO:	mout.kundenserver.de
Date:	Wed, 30 Jan 2019 22:23:03 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	Dan Bonachea <dobonachea AT lbl DOT gov>
Cc:	"E. Madison Bray" <erik DOT m DOT bray AT gmail DOT com>, cygwin AT cygwin DOT com,
	gasnet-devel AT lbl DOT gov
Subject:	Re: Bug: Incorrect signal behavior in multi-threaded processes
Message-ID:	<20190130212303.GQ3912@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	Dan Bonachea <dobonachea AT lbl DOT gov>, "E. Madison Bray" <erik DOT m DOT bray AT gmail DOT com>, cygwin AT cygwin DOT com, gasnet-devel AT lbl DOT gov
References:	<CAJTO8-bD0jPR3Vyr84Z_4BUdh3pPiZ-9ekeMBFUOFJRn5e0wQQ AT mail DOT gmail DOT com> <CAOTD34bXKQSjbce_+qNb-9GaFu88Q3o_Qw0t4oC9yK4+A7eNiA AT mail DOT gmail DOT com> <CAJTO8-ZLqP=_d-zQtFDv=syz4mfsrDRM1YBryrcL_Rp+Wt5q=w AT mail DOT gmail DOT com> <CAOTD34Z_gYcf_X3RDVqL61ME0ZDfti=ToPqm9cxoyTOisz94qg AT mail DOT gmail DOT com> <CAJTO8-b3bQX-ruNvhgi5QujW_g6hAKiMZjodNKqRY87qmXbjpQ AT mail DOT gmail DOT com> <20190130104421 DOT GC3912 AT calimero DOT vinschen DOT de> <20190130154804 DOT GJ3912 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20190130154804.GJ3912@calimero.vinschen.de>
User-Agent:	Mutt/1.10.1 (2018-07-13)

--0VNbQffo0Gc48lc+
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jan 30 16:48, Corinna Vinschen wrote:
> On Jan 30 11:44, Corinna Vinschen wrote:
> > On Jan 29 18:21, Dan Bonachea wrote:
> > > > A minimal test program is copied below and also available here:
> > > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=3D589
> > >=20
> > > > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > > > specifically requires that any given signal should be delivered to
> > > > exactly one thread. Also the spec for abort (p.565) requires the
> > > > signal to be delivered as if by `raise(SIGABRT)` (p.1765) aka.
> > > > `pthread_kill(pthread_self(),SIGABRT)` (p.1657), which implies
> > > > any registered SIGABRT handler should run only on the thread
> > > > which called abort().
> > >=20
> > > Poking around further, I find that replacing the signal generation
> > > code in the test program for all cases with :
> > >=20
> > >   pthread_kill(pthread_self(),sigid)
> > >=20
> > > generates compliant signal delivery behavior!
> >=20
> > Thanks, I fixed that in Cygwin.  It will be part of the 3.0 release.
>=20
> I think I have a solution for the SISEGV misbehaviour.  I have to
> test it a bit but this may make it into Cygwin 3.0 if all is well.

Please try the latest developer snapshot from https://cygwin.com/snapshots/
or the new 3.0.0-0.3 test release.  I hope this fixes the problem
sufficiently.


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--0VNbQffo0Gc48lc+
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxSFbYACgkQ9TYGna5E
T6CPHA//Whqn+DH8dIsnsCY63YopK5UsMFyJsKyCtqIQlToFcQoiM1FKmTVBtwoS
+0OYyZn8qlCQK2WxDkMDf5js7Ab1g92mMn4FcR5b37wDDQosnQ5eh+CSddy7InmM
VGPZVFOGhv/p6DpEO6SiAASXx5jwsUVFnPo/jItezes/AMlOas/vYNiZ8azOlNEd
u+arsOwWMVDmHcGGiYeMfnJSj55fC0gZtmsWfkPupB9mBW97Z7csVRuIUzwrKPQo
EPIq7l36yWxcvuDIgPEWmKIUqYff6Z5rG26yDL7V0Nghx78ySegdThEKKth7zVuz
EBO3UTniC20uAIAMYMF+KLTCo7mv96HS2Yy25pZfSQyxXg/tJhbRrN+kx7zCf544
+cr7s5ff02oWFnlUg/YsXhC7vT6SbGV4/Oz7sc5O9aWa2tfelAj62tqAT7wotUWP
NW7lLsV6P618UcuWHnplOXvARZKRpwmMLrR5RJmSPAXXSjkI6QI5hsokcNTZvW+M
QbmfovLTKqBx/ZjFTp5bIvsgeDz+M30+5+uluVl21Pg9z1TmiIcx48kraimluP9/
QXLtHIQK06/jHVJ8eNnfxtjDy4A5s4mZQn0AcTj6eu2cTZKAYePW7n1oRITE4Apv
zXELWCzVINGB1jJjqrwHTzS8SZerGn/jusbNyYh2asKcXd4LONk=
=SM7I
-----END PGP SIGNATURE-----

--0VNbQffo0Gc48lc+--

- Raw text -