Just finished watching Martin's Boston lecture about errors and compilers. Very useful lecture, but I have a couple of questions:
- On MVSC, when you enable
/analyze
for_Printf_format_string_
, the compilation time gets extremely long. Not only that, but suddenly a bunch of dump warnings pop up (I'm already using/W4
). Is the expected default behavior? I can manually disable all those warnings but is there any way to stop the compilation time from getting long? I could be wrong but it seems like/analyze
also doesn't play nicely with#pragma warning(push, 0)
. It keeps complaining about something in "Windows.h" so I tried disabling it just for external code like in the video but nothing seems to change. - Address Sanitizer is a great tool but it doesn't seem to work well with debugger. I'm currently using raddbg, so maybe Visual Studio would have better support. Starting the same exe in the debugger somehow is way slower than just starting from the shell. It complains about some missing sanitizer DLLs so I must start raddbg with PATH including the build tool. When ASAN catches something, I'm always at some deep call stack and need to navigate back up. Am I doing something wrong? Also, Is there any way to visualize ASAN in the debugger?