T
Tom Kacvinsky
Guest
I am using the latest version of Visual Studio 2017 Professional edition. I can set a breakpoint, but it is never hit thought I know for certainty it should be hit. What would you need from me in order to diagnose this problem? We do build from the CLI (not the GUI) so I am wondering if the PDB we generate are not quite correct. I did a repair of the Visual Studio installation but that did not help. I take the defaults for environment variables given by vcvars64.bat, and this is my compiler invocation
cl /bigobj /Zc:__cplusplus /EHsc /FS /GR /MD /MP /nologo /Zi /GS- <filename.cpp>
it may be of worth noting that we use cmake + jom (cmake -G 'NMake Makefiles JOM') for parallel compilation, which is why I had to add the /FS option. Perhaps this is messing with the PDB file generation?
Thanks,
Tom
Continue reading...
cl /bigobj /Zc:__cplusplus /EHsc /FS /GR /MD /MP /nologo /Zi /GS- <filename.cpp>
it may be of worth noting that we use cmake + jom (cmake -G 'NMake Makefiles JOM') for parallel compilation, which is why I had to add the /FS option. Perhaps this is messing with the PDB file generation?
Thanks,
Tom
Continue reading...