On Aug  4 00:44, Noah Misch wrote:
> The attached demonstration program blocks signals (with sigprocmask()) to
> achieve mutual exclusion between signal handlers.  It aborts upon receipt of a
> blocked signal.  On "CYGWIN_NT-10.0 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64",
> signals regularly arrive despite being blocked.  Essential parts of the
> program include handling two signal numbers and having handlers run for at
> least 1-2ms; this problem goes away if I remove one of those attributes.
> GNU/Linux, AIX, Solaris, and "CYGWIN_NT-6.0 1.7.27(0.271/5/3) 2013-12-09 11:57
> i686" never deliver a blocked signal to this program.  I think this Cygwin
> behavior is non-conforming.

Thanks for the testcase.  I debugged this a while today but the problem
is far from trivial, apparently.  Don't hold your breath for a quick
solution.


Corinna

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