X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_FC X-Spam-Check-By: sourceware.org Message-ID: <4E596F50.3050205@acm.org> Date: Sat, 27 Aug 2011 15:27:28 -0700 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: STC for libapr1 failure References: <4E56EB24 DOT 5000505 AT acm DOT org> <20110826111509 DOT GH10490 AT calimero DOT vinschen DOT de> <20110827203706 DOT GA15411 AT calimero DOT vinschen DOT de> In-Reply-To: <20110827203706.GA15411@calimero.vinschen.de> Content-Type: multipart/mixed; boundary="------------090606020903050607050304" X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 --------------090606020903050607050304 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 8/27/2011 1:37 PM, Corinna Vinschen wrote: > On Aug 26 13:15, Corinna Vinschen wrote: >> On Aug 25 17:39, David Rothenberger wrote: >>> For a while now, the test cases that come with libapr1 have been >>> bombing with this message: >>> >>> *** fatal error - NtCreateEvent(lock): 0xC0000035 >>> >>> I finally took some time to investigate and have extracted a STC >>> that demonstrates the problem. >> >> Thanks a lot for the testcase. In theory, the NtCreateEvent call should >> not have happened at all, since it's called under lock, and the code >> around that should have made sure that the object doesn't exist at the >> time. >> >> After a few hours of extrem puzzlement, I now finally know what happens. >> It's kinda hard to explain. >> [... very good description of flock problem ...] > > Please test the latest snapshot. It should fix this problem, as well as > a starvation problem with signals (and, fwiw, thread cancel events) in > flock, lockf, and POSIX fcntl locks. The new snapshot runs the flock STC. Thanks! I've been building libapr1 without F_SETLK support for a while since it was also triggering the "NtCreateEvent(lock): 0xC0000035" error. Since you mentioned fcntl, I tried re-enabling the fcntl mutexes. They still trigger the error. I've attached a similar STC that uses fcntl instead of flock. -- David Rothenberger ---- daveroth AT acm DOT org "It's what you learn after you know it all that counts." -- John Wooden --------------090606020903050607050304 Content-Type: text/plain; name="stc-fcntl-fork.c" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="stc-fcntl-fork.c" /*********************************************************************** * This is a STC that causes the following error on my test machine: * NtCreateEvent(lock): 0xC0000035 * * It tries to use fcntl() for file locking. It creates a temporary * file, the uses fork to spawn a number of children. Each child opens * the file, then repeatedly uses fcntl to lock and unlock it. * * This test was extracted from the APR test suite. * * Compile: gcc -Wall -o stc-fcntl-fork stc-fcntl-fork.c ***********************************************************************/ #include #include #include #include #include #include #define MAX_ITER 2000 #define CHILDREN 6 /* A temporary file used for fcntl. */ char tmpfilename[] = "/tmp/fcntlXXXXXX"; struct flock mutex_lock_it; struct flock mutex_unlock_it; /* Fork and use fcntl to lock and unlock the file repeatedly in the child. */ void make_child(int trylock, pid_t *pid) { if ((*pid = fork()) < 0) { perror("fork failed"); exit(1); } else if (*pid == 0) { int fd2 = open(tmpfilename, O_RDWR); if (fd2 < 0) { perror("child open"); exit(1); } int rc; int i; for (i=0; i