On Apr  5 02:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> >> I can’t push this through your list spam filter.  Another attempt...
> 
> I was trying a few times, and finally deleted the strace attachment.  Let's 
> see if this will go through.
> Excuse me for being a bit straightforward, but the spam filter this list is 
> using is *really* stupid!
> 
> > Still, you're missing the cygcheck log,
> 
> Cygcheck log was attached to an earlier message from today (thread: 
> exe.stackdump is always empty).
> 
> > and a simple testcase would be helpful
> 
> Here you go:
> [...]
> Windows event log immediately recorded 10 new events, like so:
> 
> Error 4/4/2014 10:02:34 PM    cygserver       0       None
> Error 4/4/2014 10:02:33 PM    cygserver       0       None
> Error 4/4/2014 10:02:32 PM    cygserver       0       None
> Error 4/4/2014 10:02:31 PM    cygserver       0       None
> Error 4/4/2014 10:02:30 PM    cygserver       0       None
> Error 4/4/2014 10:02:29 PM    cygserver       0       None
> Error 4/4/2014 10:02:28 PM    cygserver       0       None
> Error 4/4/2014 10:02:27 PM    cygserver       0       None
> Error 4/4/2014 10:02:26 PM    cygserver       0       None
> Error 4/4/2014 10:02:25 PM    cygserver       0       None
> 
> (each having exactly the same message: cygserver: PID 1944: cygserver: error 
> getting signal_arrived to server (6))

Thanks, I can reproduce the issue.  I'll investigate.


Corinna

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

Attachment: pgpIHGQs9TrPi.pgp
Description: PGP signature

Reply via email to