id summary reporter owner description type status milestone component version severity resolution keywords cc 8494 Added comments how to solve the priority inversion problem Peter Brockamp John Maddock "Hello! This is //not// a bug but just an added documentation: With Real Time OSes there does exist a general problematic scenario, called ""priority inversion"" (see http://en.wikipedia.org/wiki/Priority_inversion). When using POSIX semaphores a certain default is being used by every OS if not some deviating attributes are used to instanciate a semaphore object. boost in general uses mainly the OS-defaults, which basically is fine. However for RTP's (Real Time Processes) !VxWorks does use a POSIX-semaphore object which does //not// adhere to the priority inversion scenario. This could possibly lead to a deadlock! I added some documentation how to circumvent this problem. This is being done by changing the defaults the OS uses for semaphores, and thus does not include any changes in boost's code (and could thus not be comitted into boost) but on the contrary includes changes in the OS code itself and afterwards rebuilding the OS (which is supported for !VxWorks)." Patches closed To Be Determined config Boost 1.54.0 Cosmetic fixed vxworks priority inversion