Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com In-Reply-To: <20050404103824.GS1471@cygbert.vinschen.de> References: <424D0232 DOT 5060305 AT smousseland DOT com> <20050401090414 DOT GD7415 AT cygbert DOT vinschen DOT de> <424D2B0B DOT 8000604 AT smousseland DOT com> <20050401121143 DOT GD1471 AT cygbert DOT vinschen DOT de> <424D5C64 DOT 5050706 AT smousseland DOT com> <20050401160749 DOT GH1471 AT cygbert DOT vinschen DOT de> <4250E410 DOT 1060708 AT smousseland DOT com> <20050404103824 DOT GS1471 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9305417ca9a2f2601ad20b83801d2f92@smousseland.com> Content-Transfer-Encoding: 7bit Cc: cygwin AT cygwin DOT com From: Vincent Dedun Subject: Re: ipc, sockets and windows sp2 Date: Mon, 4 Apr 2005 15:13:40 +0200 To: cygwin AT cygwin DOT com Corinna Vinschen wrote : > 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? > i have no idea how to do this, i'm not a good system programmer. further more, i have a slow computer, and recompiling cygwin is long. I even don't know how to active debugging (dprintf) on cygwin dll. I just saw a strange stuff : in sysv_sem.cc (cygserver) at end of semop function (:done2 label), the mutex is released after waking up waiting process, shouldn't it be the inverse ? i tried to test this, but when i modify cygwin sources and compil, my cygwin0.dll is not updated, i don't want to recompil everything each time, it take too longs. Kraken -- 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/