boost::thread within a dll
Hello list, I'm facing some problems with a dll that uses boost::thread, boost::mutex and boost::condition_variable. Currently i am clueless about what is causing the problem and wanted to know if it is ok to use boost::thread and the others aforementioned within a dll. Basically, in a singleton in the dll, some threads are created and consume tasks (wrapped with boost::bind) from a queue, using boost::mutex to avoid concurrency problems and boost::condition_variable to sleep and wake, depending on emptiness of the task queue. Sorry for the brief and rapid description of my problem. Could anyone point to me if using these might cause problems with dlls? Thank you all, -- Matheus Araújo Aguiar Computer Scientist matheus.pit@gmail.com
I'm facing some problems with a dll that uses boost::thread, boost::mutex and boost::condition_variable. Currently i am clueless about what is causing the problem and wanted to know if it is ok to use boost::thread and the others aforementioned within a dll. Basically, in a singleton in the dll, some threads are created and consume tasks (wrapped with boost::bind) from a queue, using boost::mutex to avoid concurrency problems and boost::condition_variable to sleep and wake, depending on emptiness of the task queue. Sorry for the brief and rapid description of my problem. Could anyone point to me if using these might cause problems with dlls?
What problems? Did you mention any problem? I'm using boost.thread within a COM dll and didn't encounter any problems.
On Tue, Oct 26, 2010 at 7:00 PM, Igor R
I'm facing some problems with a dll that uses boost::thread, boost::mutex and boost::condition_variable. Currently i am clueless about what is causing the problem and wanted to know if it is ok to use boost::thread and the others aforementioned within a dll. Basically, in a singleton in the dll, some threads are created and consume tasks (wrapped with boost::bind) from a queue, using boost::mutex to avoid concurrency problems and boost::condition_variable to sleep and wake, depending on emptiness of the task queue. Sorry for the brief and rapid description of my problem. Could anyone point to me if using these might cause problems with dlls?
What problems? Did you mention any problem? I'm using boost.thread within a COM dll and didn't encounter any problems.
Thing is i do not really know the problems, because i am not the one coding the dll. But basically it seems to be seg. faults and stalled threads. Just wanted to ask if it is not recommended to use those libraries within a dll. Guess it is allright then. Thanks for the attention,
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Matheus Araújo Aguiar Computer Scientist matheus.pit@gmail.com
Thing is i do not really know the problems, because i am not the one coding the dll. But basically it seems to be seg. faults and stalled threads. Just wanted to ask if it is not recommended to use those libraries within a dll. Guess it is allright then.
Segfaults and stalled threads are usually general symptoms of improper memory management and race-condition handling in a multi-threaded environment. This is most likely unrelated to the executable type (dll or exe).
participants (2)
-
Igor R -
Matheus Araújo Aguiar