title: Boost Thread Access Violation in Boost Log on shutdown
body: <p>I have an application that uses boost logging. During shutdown, it gets an access violation on a null pointer access. When I step through the code to the point of failure, it appears that the boost::log dll is being de-allocated and then boost::thread code tries to access the memory that was once occupied by the log dll.</p>
  
  <p>I am not using any boost threads in my own code, and so assume the boost-thread dll is used by boost log.</p>
  
  <p>To ensure all sinks are destroyed prior to shutdown, I am calling: core->flush() and core->remove_all_sinks()</p>
  
  <p>I am using boost 1.60 and have also tried this with boost 1.63. Same result.</p>
  
  <p>Is there a way to ensure the boost logging core is shut down fully before exit / unload the dlls?</p>