[boost] boost::log access violation with global objects destructors

Hello, Boost.Log creates an access violation when global objects being destructed attemps to log something. The doc says that I have to keep a shared_ptr to the core, but even doing so doesn't seem to work. I created a simple testcase here: http://codepad.org/pr8fAiZ2 The access violation location changes when the code change so I'm not sure how to handle this. This happens on Windows XP with boost 1.43 and the latest boost.log source from the svn. Thanks in advance! Philippe