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=ZKNnILxlyEIiQNrBbq8sQNWJP/gkolPmBRWUT+b2Lzb5lbFZjKT8W
	zNo1awilNCK47t3f8OtZTZkkPVI2H+WQOPDTpuZEAZKAzoUmVSe9JEpM1sY8pRz1
	ynpsafFlTuTaA0FEgcF9CqNXYJI70son8p5DZKGEY2NvkVXmO53+AM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 30 Jan 2019 16:48:04 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Dan Bonachea <dobonachea@lbl.gov>
Cc: "E. Madison Bray" <erik.m.bray@gmail.com>, cygwin@cygwin.com,
        gasnet-devel@lbl.gov
Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes
Message-ID: <20190130154804.GJ3912@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: Dan Bonachea <dobonachea@lbl.gov>,	"E. Madison Bray" <erik.m.bray@gmail.com>, cygwin@cygwin.com,	gasnet-devel@lbl.gov
References: <CAJTO8-bD0jPR3Vyr84Z_4BUdh3pPiZ-9ekeMBFUOFJRn5e0wQQ@mail.gmail.com> <CAOTD34bXKQSjbce_+qNb-9GaFu88Q3o_Qw0t4oC9yK4+A7eNiA@mail.gmail.com> <CAJTO8-ZLqP=_d-zQtFDv=syz4mfsrDRM1YBryrcL_Rp+Wt5q=w@mail.gmail.com> <CAOTD34Z_gYcf_X3RDVqL61ME0ZDfti=ToPqm9cxoyTOisz94qg@mail.gmail.com> <CAJTO8-b3bQX-ruNvhgi5QujW_g6hAKiMZjodNKqRY87qmXbjpQ@mail.gmail.com> <20190130104421.GC3912@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="wwU9tsYnHnYeRAKj"
Content-Disposition: inline
In-Reply-To: <20190130104421.GC3912@calimero.vinschen.de>
User-Agent: Mutt/1.10.1 (2018-07-13)

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

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.

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.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--wwU9tsYnHnYeRAKj
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxRxzQACgkQ9TYGna5E
T6DAmg//VKo6j/PDpVef57DHbrefwxE7G2zHi3F8HTmzxwSpjaTGZpYhcO+S0Yu7
QCuppX7viFBC1bom1TB1rrlsUGLDfsZFEKnT0aFZ3dkRpAiE76UU1Fsrm+2BauUY
wX1+TwsAHKxb/VV8bK4AABqpbQYmcWhyqCEfVtoSLn0E08tKsZOq1rCRvSahWa14
eJkFDZbCOxtBK31hY+1oy7ESimUrwmhPJErIjIU5GSIMB7xCYoKoRcoAfjNHY/vM
HyUoS+K5UYhIqZV355vFGy4hFT7a0PfYsSr2Y/0nv4QRhbDUMfzryoNW9m2P4vJQ
UFTy6bFV+SeeW8t3Rsl6EraW7zL6/TDGhxS92PK9ls8mfF8Ehxqphfq9FBxPqvzC
q6tjpMqJs2yMpPruTcuHeL2TF+jW4aNqZpXZVOKx8i4gjP6llcrkcJKCvtXLyi5f
6qOGRVKYHKh9oLLNjTH0kMqZ9vAM2t+63bbVIfevdsAvDB4SYHEWECOyllTo3zzT
MLcEJOf0hwGKIkEAaP9ssFuPLcHTas5es+9ef14QV2MURyPNcbVAyVJaoa2HuwhA
+ywmRFVNFE8Bh9RBqo48M0469WjuUHo16i4RzvebZCg0YINfmGhElvw6ka9mCa20
Spz4uYEexlI9sVEckBlXpdBbHxbpMMi5tuO5Q3ML5RSRqMfpqv8=
=MImh
-----END PGP SIGNATURE-----

--wwU9tsYnHnYeRAKj--