title: Occasional crash from memcpy which I am not using in my program directly
body: <p>I am working on the largest project I've ever worked on, and I've never debugged something like this, so I don't know where to get started.</p>
  
  <p>Some info on the crash:
  I am using Visual Studio, and the debugger is completely useless.  The only information it gives me is that it appears to be happening during a call to "memcpy".  The call stack is completely empty except for the memcpy function, and the local variables are listed but it does not have values for any of them.</p>
  
  <p>It happens occasionally on any computer.</p>
  
  <p>It does not ALWAYS happen under any (known) condition, but it only ever happens under a few conditions.  In particular it only happens when a particular type of object is destroyed, although that's not necessarily the direct cause, and investigating the destruction process has not been helpful.</p>
  
  <p>A little more about the project:
  It is a game using SFML 2.0, linked statically.
  I am not calling memcpy anywhere in my own code.</p>
  
  <p>Some questions:
  Where could the call to memcpy be coming from?  Is it in SFML or elsewhere?
  How do I (using visual studio) get more information on a crash when the debugger isn't working?</p>