DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc:content-type; q=dns; s=default; b=nPSB
	CPk4K3aCy+fDzPrJQ55WAxn37TyK5jOP0FQcGVvFypWQMs1MLhTpoSxyyyGMcZv0
	JCZWTw4pyPV1uWjZBzFYPH/Xg0jttBCawQ/DNxHzrqMpG+9U4YrDNd2zgD395F7V
	OyVQXnGGRwy3jHpp2iHEbuIyLb7PQu5Ae6g2J9Q=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
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> <20190130154804.GJ3912@calimero.vinschen.de> <20190130212303.GQ3912@calimero.vinschen.de>
In-Reply-To: <20190130212303.GQ3912@calimero.vinschen.de>
From: Dan Bonachea <dobonachea@lbl.gov>
Date: Wed, 30 Jan 2019 19:11:29 -0500
Message-ID: <CAJTO8-Z18U+g+8kzRxpY-g7Ds5CGpuJG0-n6Pmevt_2dPS60AQ@mail.gmail.com>
Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes
To: cygwin@cygwin.com, Dan Bonachea <dobonachea@lbl.gov>
Cc: "E. Madison Bray" <erik.m.bray@gmail.com>, gasnet-devel@lbl.gov
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> > > > Poking around further, I find that replacing the signal generation
> > > > code in the test program for all cases with :
> > > >
> > > >   pthread_kill(pthread_self(),sigid)
> > > >
> > > > generates compliant signal delivery behavior!
> > >
> > > 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.
>
> 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.

Hi Corinna -

I've installed the 3.0.0-0.3 test release on my workstation and
confirmed that it fixes all the reported misbehaviors in the test
program.
It also appears to fix the signal-related problems encountered in our
multi-threaded production code.

Thanks so much for the prompt fixes!
-D

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