pthreads, cygwin and pthread_mutex_lock not blocking

Gary R. Van Sickle g.r.vansickle@worldnet.att.net
Thu Jun 2 00:53:00 GMT 2005


I'm coming to this particular party pretty late, so if my comments are
totally off-base or have been already covered, please disregard:

> On May 31, 2005, at 10:50 AM, David Rothenberger wrote:
> 
> > On 5/31/2005 10:15 AM, Peter Rehley wrote:
> >> Well, here is a simple test case, but turns out I wasn't using the 
> >> latest version.  I was having the problem on 1.5.12,  I 
> haven't been 
> >> able to get a good build with cygwin 1.5.17-1.  It builds 
> and I can 
> >> run the install script, but when I put the dll in place I see the 
> >> message "cygheap magic number mismatch detected", and gcc doesn't 
> >> want to work.
> >

On some occaisions I've had to reboot the machine for some reason (WinXP),
not just kill all Cygwin processes, in order to successfully replace the
cygwin1.dll with a different version.  I've had the file copy go fine,
indicating no process is currently using it, but then got the error you're
seeing when attempting to run any Cygwin apps.  If you're still set up to
build the Cygwin DLL, I'd suggest trying it again with your proposed
change(s) and see if this gets you over that hump.

FWIW, I get this running your fork_test.c app on snapshot 20050528, compiled
with the latest Cygwin "exp" gcc and binutils:

 GaryV@123456 ~
 $ ./a.exe 
 thread locked 0
 I'm the parent
 heh, I'm done 45
 I'm the child
 
 GaryV@123456 ~
 $ ahh, what a good nap
 << waits for CR >>

which I believe indicates the problem you reported is still present in that
snapshot.

-- 
Gary R. Van Sickle
 


--
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/



More information about the Cygwin mailing list