On Wed, Dec 23, 2009 at 3:45 PM, Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx> 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. Sorry, let me be clearer here. The *first* lock is through the fast path of the lws CAS operation. All subsequent locks take the form of a futex wait. All subsequent unlocks are a futex wake. Cheers, Carlos. -- 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
