On Wed, May 12, 2010 at 7:13 AM, Rob Yull
The call stack (>>> is where the exception is caught).
KernelBase.dll!_RaiseException@16() + 0x58 bytes
msvcr100d.dll!_CxxThrowException(void * pExceptionObject, const _s__ThrowInfo * pThrowInfo) Line 157 C++
BoostTest.exe!boost::copy_exceptionboost::exception_detail::bad_alloc_ (const boost::exception_detail::bad_alloc_ & e) Line 47 C++
BoostTest.exe!boost::exception_detail::get_bad_alloc<42>() Line 80 + 0x9f bytes C++
BoostTest.exe!`dynamic initializer for 'boost::exception_detail::exception_ptr_bad_alloc<42>::e''() Line 94 + 0x28 bytes C++
msvcr100d.dll!_initterm(void (void)* * pfbegin, void (void)* * pfend) Line 873 C
BoostTest.exe!__tmainCRTStartup() Line 473 + 0xf bytes C
BoostTest.exe!mainCRTStartup() Line 371 C
kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes
ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes
ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes
Did something change between 1.42 and 1.43 that would cause this?
May be related to changes I made in Boost Exception however I can't reporduce the crash with the latest trunk revision an MSVC 9. Anything more specific you can add?
I do have my compilers (VC2005 Pro and VC 2010 Express) set to break on exceptions, which is how I really first noticed it (though it does show up in the output window along with all of the loaded symbols as well). When the debugger halts, it does look like hitting continue doesn't break execution. There may be a try/catch block somewhere handling it, so it might be something ignorable (just annoying). I guess the better way to say it is at some point during the static initialization, boost 1.43 is throwing a bad_alloc for some reason, but may be handling it. -Rob Yull