On 12/03/2010 08:10 PM, Paul Bergen wrote:
Basically, I use bjam like this:
bjam toolset=msvc-9.0 variant=release threading=multi link=shared
This would suggest that you're building Boost in "Release" configuration.
boost_thread-vc90-mt-gd-1_44.dll!boost::`anonymous namespace'::thread_start_function(void * param=0x00748fc0) Line 169 C++ msvcr90d.dll!61e5dfd3() msvcr90d.dll!61e5df69()
This suggests that you're linking and running against the "Debug" CRT.
kernel32.dll!77143677()
Run your exe in a good debugger (like WinDbg or NTSD) and see if you have multiple versions of MSVCR*.dll being involved. Or you may have some modules being linked statically and other dynamically. You can probably look at the modules in the MSVS IDE too. The 'depends.exe' tool can be useful for tracking this down, too. Did perhaps you add a linker directive to bring some Boost .libs manually? Did perhaps that get set for both Debug and Release when it really needed to be specified separately? Just some thoughts. - Marsh