title: Memory heap corruption and GFlags/windbg
body: <p>I have an application wich produce memory heap exception (corruption).</p>
  
  <p>On the web I have found this kind of sentence : </p>
  
  <blockquote>
    <p>"GFlags.exe: A heap debug program. Using GFlags, you can establish
    standard, /full, or /dlls heap options that will force the operating
    system to generate access violations and corruption errors when your
    program overwrites heap memory. "</p>
  </blockquote>
  
  <p>But concretely how can I with GFlags or Windbg find the line in my source code which causes the bug?</p>
  
  <p>Is there any good/synthetic paper on the web?</p>