On Feb 23 07:59, Richard Elberger wrote:
> Awesome ;)  Thanks so much I will keep a look out for it and verify on
> my end that the perl unit test works as expected.
> 
> 
> > On Feb 23, 2015, at 7:42 AM, Corinna Vinschen <corinna-cyg...@cygwin.com> 
> > wrote:
> > 
> > Hi Richard,
> > 
> > On Feb 21 16:17, Richard Elberger wrote:
> >> Hello,
> >> 
> >> I found this while trying to compile perl 5.20.1 on latest cygwin64
> >> (just updated yesterday).
> >> 
> >> Effectively, sigaddset is adding a signal along these lines.  If
> >> signal x is less than 32, then two signals are added: x and x+32.  If
> >> signal x is greater than 32, then again two signals are added, x and
> >> x-32.
> >> 
> >> It’s been far too many years since I’ve written C but the attached
> >> code snippet to prove it (hopefully it proves it) … and running the
> >> same “code” (I put that in quotes because it’s like preschool C) on
> >> any Linux works as expected - just adding the one signal.
> >> 
> >> This is causing the sigset.t test for the POSIX module in perl core to
> >> fail.  There are a ton of other failures in testing 5.20.1 core but
> >> hopefully they’re not all cygwin related like this one.
> > 
> > Thanks a lot for the testcase.  I fixed the problem (an int overflow
> > computing a bit mask) in CVS.  I'll generate a developer snapshot on
> > https://cygwin.com/snapshots/ and probably another Cygwin 1.7.35 test
> > release soon.  Both will contain that patch.

Snapshots are up.  Please give it a try.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpTdaF8uczfp.pgp
Description: PGP signature

Reply via email to