> As you can imagine a program that relies on 'fast' mutex behaviour > will not function correctly on a system which uses 'error checking' > (i.e. ownership) mutexes (the reverse case might work - I haven't > tried it ;)).
A program the relies on undefined behaviour is broken. > The workaround is to override the brain damaged default with: It's a very sane default because the performance difference is astronomical > #ifdef __linux__ Far better is if (defined __linux__) && defined(DEBUG_MUTEXES) then you can build for debug or for performance as needed with a compile option. Even better still for many applications is not using pthreads in the first place. The fundamental models pthreads use are basically 'everything is shared, nothing is locked unless you remember to do so' and there is no object access v locking validation. In short it's got default behaviour of 'break invisibly' Java at least tried to get chunks of this right. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
