Following Peter's advice, I downloaded the patched function_template.hpp and rebuilt the boost libraries. I then rebuilt both my client library (based on boost) and client application and receive the following core dump back trace. #0 0x56e58955 in ?? () #1 0xb7fd96b2 in boost::thread_group::join_all () from /home/tbarrett/boost_134/lib/libboost_thread-gcc34-mt-1_34_1.so.1.34.1 #2 0x00a3b3cc in start_thread () from /lib/tls/libpthread.so.0 #3 0x008b2c3e in clone () from /lib/tls/libc.so.6 Was there an issue in 1_34_1 with thread_group::join_all? Thanks, -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Peter Dimov Sent: Tuesday, August 26, 2008 11:28 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] [function?] exception in assign_to_own,was: (no subject) Timothy Barrett:
Forgive the previous incomplete post. I am working with boost-1_34_1 on redhat EL4 update 5.
My backtrace is: #0 0x56e58955 in ?? () #1 0xb7fd55f5 in boost::function0
boost::function_base >::assign_to_own (this=0xb7eda390, f=@0xbffff770)
You may be encountering the thread-safety bug described in http://svn.boost.org/trac/boost/ticket/1260 I suspect that the hotfix for 1.34.x that is mentioned in #1260 is http://boost.sourceforge.net/function-1-34-fix/function_template.hpp You should try replacing your function_template.hpp with the file above and see if it helps. If you wonder how did I know where to find the hotfix - I googled 'assign_to_own' :-) _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users