Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.1

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

On Aug 14 20:47, Takashi Yano wrote:
> On Wed, 14 Aug 2019 20:41:00 +0900
> Takashi Yano wrote:
> > Hi Corinna,
> > 
> > On Tue, 13 Aug 2019 12:47:53 +0200
> > Corinna Vinschen wrote:
> > > I created a patch which *seems* to do the right thing.  I'm not
> > > yet sure it's the best solution, but it seems to do the trick, at
> > > least.
> > > 
> > > I'm just creating new developer snapshots, please try.  I'll
> > > create another test release later this week.
> > 
> > I confirmed the STC works as expected. Thank you.
> > 
> > However, it seems that signalfd still has a problem.
> > 
> > If script command (from util-linux) is terminated by '^D',
> > the following error message is sometimes shown.
> > 
> > script: poll failed: Interrupted system call
> > 
> > I have confirmed this in 32bit cygwin with bash as login shell.
> > This rarely occurs in real machine, however, often occurs in
> > virtual machine in VirtualBox.
> 
> Sorry, I forgot to mention important thing.
> 
> This occurs only in cygwin on command prompt. Not in mintty.

The only reason I can see is if sigwait_common() returns EINTR because
it was interrupted by an unrelated signal.  This in turn lets the read()
call fail with EINTR and that should be expected by the callers, in
theory.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]