On Tue, 2011-03-22 at 11:20 +0100, Holger Wirtz wrote: > I tried the same thing with the glib-pthreads wrappers, but > pthread_mutex_lock blocks until the mutex is unlocked. Perhaps this > should work with pthread_mutex_trylock()?
It depends on the mode but you could also test prior to locking if it is already 1 but then you're a but late in the game. > > You could add all kinds of fancy stuff using __FILE__, __FUNCTION__ and > > __LINE__ to detect from where the code has been called. > > Note: This only works for __GNUC__ > > Ok, this seems to be a good way to get more information where the dead > locks are located. I will try this. > > Thanks a lot! You're welcome. Erik ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
