On Tue, Dec 22, 2009 at 11:48 AM, John David Anglin <dave@xxxxxxxxxxxxxxxxxx> wrote: > Debian gdb 7.0 provides slightly different backtraces: > > (gdb) bt > #0 0x4039934c in __lll_lock_wait (futex=0x1c538, > private=<value optimized out>) > ... > > and > > (gdb) bt > #0 0x4038f92c in __lll_mutex_lock (mutex=0x1c538) Any idea why both threads would try to lock the same mutex? This is never going to work? I think we need to step back from the edge and ask ourselves what Tcl_WaitForEvent() is trying to do with the locks. Do you know? 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
