title: Debugging undebuggable application for memory corruption
body: <p>This is a bad situation: I have a large C++ application on Windows which is having a memory corruption.</p>
  
  <p>Basically I dumped the content of a float variable and found the ASCII code of "hell" from a string elsewhere which was "hello world".</p>
  
  <p>The big problem is: I can't debug it with a memory breakpoint since this is ONLY happening in release mode outside visual studio (release mode started by visual studio isn't triggering the bug, nor release with debug symbols).</p>
  
  <p>Since the application is large and operates with lots of strings, I don't know how to debug it.</p>
  
  <p>Do you have any idea on how to proceed?</p>