breakpoints not binding anymore, how to track down?
VS 2017. Updated. Windows 10.
Since a few weeks ago, all projects in VS2017 in x64 configuration stopped binding to break points.
This is in Debug config (verified that it is not creating release versions of binaries). Debug symbols are on. /Zi. Module windows shows pdb loaded. llvm pdb utils shows correct paths in exe and guid. Breakpoints should work, but don't! They used to, but now they don't.
They work in x86 config though. Friend's WIn 10 machines shows same problems.
The only common thing we did was (in addition to Windows auto updates?) to run cmake for protobuf and some related source code within last couple of weeks.
A third computer, Win 10, VS2017 (but a bit older version) doesn't show this problem (not cmake was run on that one).
Removed all .vs directories, no luck.
Repaired my VS2017 installation. No luck.
Cleared away my local VS2017 config directory as a hard clean up, no luck.
Been browsing the internets, looked hither and tither, can't seem to find the root cause.
What else can I try, short of reinstalling or upgrading to newer VS version, to fix my VS2017 x64 debugging?
Self edit for future visitors: Solved. The security software was blocking msvsmon.exe, the visual studio debugging monitor. The white list item of that exe was misconfigured. The IT fixing that got VS 2017 debugging working normally again.