On Wed, Dec 23, 2009 at 4:08 PM, John David Anglin <dave@xxxxxxxxxxxxxxxxxx> wrote: >> 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. You would be surprised how easy it is to duplicate some of these problems. We need to write a small skeleton application that does something similar to the notification done by tcl and uses pthread_cond_timedwait. Setup main to run forever signaling the child which does something and then goes back to waiting. Eventually this should lock up like it does in tcl. 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
