Timmo, In looking over signals/detail/threading_model.hpp, it looks like signals::mutli_threaded isn't thread-safe due to the way it uses scoped_lock. That is, scoped_lock is not thread-safe. I used a slightly different approach in thread_safe_signals/single_threaded.hpp (which provides a null mutex type) and multi_threaded.hpp (which provides real mutexes and is not included by default to prevent default inclusion of boost.thread headers). -- Frank
Frank Mori Hess wrote:
In looking over signals/detail/threading_model.hpp, it looks like signals::mutli_threaded isn't thread-safe due to the way it uses scoped_lock. That is, scoped_lock is not thread-safe.
Yes, I'm quite aware of that problem (I was not at the time I committed the code). It was a quick and dirty hack just when I realized how limited the Boost.Threads mutex interface was. I don't use Boost.Threads in my own project, so this discovery somehow caught me by surprise ;). I found a way around it and the problem should be gone with the next update. Regards Timmo Stange
participants (2)
-
Frank Mori Hess -
Timmo Stange