title: VS2008 C++ breakpoint becomes permanently inactive after access violation error (no executable code associated with line)
body: <p>I am reproducing the following behavior in VS2008 (native C++):</p>
  
  <ul>
  <li>attach to an executable that consumes a custom dll (for which I have the source)</li>
  <li>debug the code from the dynamic lib</li>
  <li>encounter an access violation error (probably caused by the code in the executable - closed source)</li>
  <li>break on access violation error with the attached debugger</li>
  </ul>
  
  <p>After this, no matter how many times I reattach, rebuild, restart the application, computer, any breakpoint I will set in the .dll source code becomes inactive (<em>No executable code associated with this line</em> is the alleged cause, according to VS).</p>
  
  <p>I suspect this is an issue with VS2008, as I did the same on a different machine and now I have two machines where debugging is no longer possible.</p>
  
  <p>Are there any recorded solutions of this issue? What can be done to overcome it?</p>
  
  <hr>
  
  <p>What I have done:</p>
  
  <ul>
  <li>deleting everything (the entire solution, pdbs, binaries, etc.) and starting with the code from scratch (cloning the latest version from the repository)</li>
  <li>restarting the machine</li>
  <li>changing the machine (it worked once, until the error occurred, then the other computer exhibited the same behavior)</li>
  </ul>
  
  <p>What I cannot do:</p>
  
  <ul>
  <li>change compiler/VS version</li>
  <li>debug the executable (sadly no source code available and lack of assembly skills)</li>
  </ul>