While test-driving Intel Inspector we found out that it will fail to detect memory leaks when multiple Visual C++ runtime versions are loaded in the process.
Has anyone seen this before? Does anyone know if there's a way to point the tool to the specific runtime heap management one wants to inspect.
In our case the exe module is written by us, is compiled with Visual C++ 2008sp1 (MSVCR90.DLL) and brings in a plain C DLL that is built with v2010 (MSVCR100.dll).
Thanks in advance!