I am using Intel Inspector 2016 Update 1 to inspect code compiled with Visual Studio 2008. We are getting 'uninitialised memory access' errors on use of strcmp(). Our suspicion is that the compiler has optimised to read 4 bytes ahead at a time for performance, even if that is beyond the length of the string. So while the tool is technically correct it has no implications for stability.
Is this a known issue, is there a way to stop reporting on strcmp?
In general speaking, Intel Inspector 2016 u1 -
Supported Microsoft Visual Studio* versions:
o Microsoft Visual Studio* 2012
o Microsoft Visual Studio* 2013
o Microsoft Visual Studio* 2015
Microsoft Visual Studio* 2008 is not in the list. If you think that is "Guard zone size" issue - you can create a Custom Analysis for detecting memory problem, then Edit - check "Enable guard zones" to change "Guard zone size" then retry?