On 2/15/2012 7:38 AM, Corinna Vinschen wrote: > Did I mention that I hate synchronization problems? Anyway, I think I > found the problem. I applied a patch which fixes the problem for me > and, surprise!, the flock test still runs fine, too. I've just uploaded > a new snapshot. Please give it a try.
All the procmutex tests pass now! Awesome! But... now one of the flock tests is failing. It takes a while to extract a STC from the APR test suite because everything is written in APR-ese and I have to convert every APR call into the base C library calls. I'll work on that over the next day or three. The gist of the test that's failing is this: * Create a file. * Get an exclusive flock on it. * Spawn a child process that attempts to get an exclusive, non-blocking lock on the file. The test is expecting that the child will not be able to get the lock, but the child is able to. -- David Rothenberger ---- daver...@acm.org Hubbard's Law: Don't take life too seriously; you won't get out of it alive. -- 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