Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 4 Apr 2005 12:38:24 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: ipc, sockets and windows sp2 Message-ID: <20050404103824.GS1471@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <424D0232.5060305@smousseland.com> <20050401090414.GD7415@cygbert.vinschen.de> <424D2B0B.8000604@smousseland.com> <20050401121143.GD1471@cygbert.vinschen.de> <424D5C64.5050706@smousseland.com> <20050401160749.GH1471@cygbert.vinschen.de> <4250E410.1060708@smousseland.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4250E410.1060708@smousseland.com> User-Agent: Mutt/1.4.2i On Apr 4 08:52, Vincent Dedun wrote: > However, semaphores still doesn't work properly. > There is no more problem with semop not waiting, but with quick > semaphores locking unlocking. > > I attach a new testcase, which is the same as previous one, except each > child task will lock the semaphore, wait 100ms, then release the > semaphore and die. Each time a child dies, a new one is created to keep > 10 running childs. I'm wondering, since you're building Cygwin from source anyway, if you're not interested to debug this further or even track it down to its source? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/