On Jan 30 19:11, Dan Bonachea wrote:
> 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!

Thanks for testing!


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer