This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: SIGCHLD is not delivered
- From: Andreas Steenpaß <steenpass at mathematik dot uni-kl dot de>
- To: cygwin at cygwin dot com
- Date: Fri, 29 Mar 2013 19:40:49 +0100
- Subject: Re: SIGCHLD is not delivered
- References: <5154460D dot 4090101 at mathematik dot uni-kl dot de> <20130329132942 dot GD3460 at ednor dot casa dot cgf dot cx>
Le 29/03/2013 14:29, Christopher Faylor a écrit :
> On Thu, Mar 28, 2013 at 02:30:53PM +0100, Andreas Steenpa? wrote:
>> I have noticed that sometimes SIGCHLD is not delivered when a child
>> process exits. I can reproduce this behaviour reliably under the
>> following, very special circumstances:
> I've uploaded a new snapshot which seems to fix this problem. Before
> running it, I could see a rare when I ran your test case in a loop.
> After, I never saw a hang.
>
> Thanks for the test case and please give the snapshot a try.
I've installed the newest snapshot and recompiled the test case, but it
still hangs on my system. I'm sorry for interfering with your release.
Is there any further information I could provide to solve this issue?
Just to be sure:
$ uname -a
CYGWIN_NT-6.1-WOW64 zoppo 1.7.18s(0.263/5/3) 20130329 13:18:55 i686 Cygwin
My installation of Windows runs in a virtual machine. Could this maybe
influence the race conditions? I've noticed that the resolutions I get
with clock_gettime(CLOCK_REALTIME, ...); are quite coarse (a few
milliseconds!) in comparison to my Linux system (nanoseconds), or is
this a general Cygwin thing?
Best regards,
Andreas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple