On Wed, 23 Dec 2009, Carlos O'Donell wrote: > On Wed, Dec 23, 2009 at 3:39 PM, John David Anglin > <dave@xxxxxxxxxxxxxxxxxx> wrote: > > The deadlock occurs at the third call to Tcl_MutexLock in NotifierThreadProc > > (tclUnixNotfy.c:997). This is in a while(1) loop, so I have to think > > the previous call to Tcl_MutexUnlock failed, possibly because of a call > > to Tcl_ConditionNotify. > > You might get a better idea if you run this under strace and look at > the futex syscalls being made. You won't see the locks since the fast > path is through the light-weight-syscall compare-and-swap, but you > will see the unlocks, and you can count them. I would guess that the notifierMutex is locked/unlocked millions of time in a typical GCC testsuite run. So, the problem won't be easy to duplicate manually. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
