Visual Studio can't set valid breakpoint

  • Thread starter Thread starter RD Holland
  • Start date Start date
R

RD Holland

Guest
This has been driving me crazy for some time (and that's a short trip). I open a project in VS 2017 and set a breakpoint in a source file. Then I start the debugger. The break point disappears from the source file (red dot goes away). My breakpoint doesn't trip.

Why? Because somewhere in the world another programmer created a source file with the same name. Path is totally different but the base name is the same (think "server.cpp" that gets created by VS wizards all the time).

It appears to me that the debugger is ignoring the path and as soon as a DLL loads with a PDB file and that DLL has a source file with the same name, the debugger erroneously attaches to it, moves my break point and then laughs at me as I tell it just what I think about it.

How hard can this be? My project is open, I am setting a break point in a source file I have open in the project but somehow the debugger thinks I want to set a random break point in some other source file and debug it (which of course doesn't trip because that code isn't getting executed with my debugging workflow. This has been like this for ever and I have complained before to no avail.


R.D. Holland

Continue reading...
 
Back
Top