Matthew Dillon wrote: > Something in that chain of calls is passing a NULL to > __pthread_mutex_trylock().
Yep, but ... > Try this patch. It will do the same check that libc_r does. It just makes backtraces huge. Obviously passing NULL to __pthread_mutex_trylock() isn't the problem, but probably just consequence. > I'm not convinced that Qt isn't broken, though, Qt shouldn't be passing > NULL to the mutex functions, it should be passing the address of > a pthread_mutex_t which itself can be NULL, but it should be > passing NULL. Qt doesn't pass NULL, it's glib. It doesn't mean that problem may not be in Qt though. Just to be sure I tested these examples in some other platforms and all these examples work fine in Linux, OpenBSD and FreeBSD. I updated static binaries tarball to include debug info from glib as well. http://leaf.dragonflybsd.org/%7Ehasso/qt44-threaded-tests.tar.bz2 -- Hasso Tepper
