We migrated to the MSVC2013 from MSVC2010 and updated VLD to the latest version from the source tree (tested with latest release 2.4.rc2 as well).
Our project uses MFC with static linkage. A couple of false positives were detected, concerning CRTs _type_info name_. In the previous version (MSVC2010) we had a fix for that which cleared the chain of _type_info names_ leaks before memory leaks detection. The problem should be supposedly fixed in MSVC2012 (not tested).
This is how the callstack looks like:
```
0x77851520 (File and line number not available): ntdll.dll!RtlAllocateHeap
f:\dd\vctools\crt\crtw32\heap\malloc.c (58): xxx.exe!_heap_alloc_base
f:\dd\vctools\crt\crtw32\heap\malloc.c (92): xxx.exe!_malloc_base + 0x9 bytes
f:\dd\vctools\crt\crtw32\eh\typname.cpp (119): xxx.exe!type_info::_Name_base + 0x7 bytes
f:\dd\vctools\crt\crtw32\eh\typinfo.cpp (28): xxx.exe!type_info::name + 0xD bytes
...
```
If it is fixed, as claimed by MS, maybe the memory leaks detection is done before the cleanup.
Some useful workaround would be to specify false positives in _vld.ini_ that would be ignored. Something like:
```
IgnoreFalsePositives = "!type_info::name ", "something else"
```
Thanks
Our project uses MFC with static linkage. A couple of false positives were detected, concerning CRTs _type_info name_. In the previous version (MSVC2010) we had a fix for that which cleared the chain of _type_info names_ leaks before memory leaks detection. The problem should be supposedly fixed in MSVC2012 (not tested).
This is how the callstack looks like:
```
0x77851520 (File and line number not available): ntdll.dll!RtlAllocateHeap
f:\dd\vctools\crt\crtw32\heap\malloc.c (58): xxx.exe!_heap_alloc_base
f:\dd\vctools\crt\crtw32\heap\malloc.c (92): xxx.exe!_malloc_base + 0x9 bytes
f:\dd\vctools\crt\crtw32\eh\typname.cpp (119): xxx.exe!type_info::_Name_base + 0x7 bytes
f:\dd\vctools\crt\crtw32\eh\typinfo.cpp (28): xxx.exe!type_info::name + 0xD bytes
...
```
If it is fixed, as claimed by MS, maybe the memory leaks detection is done before the cleanup.
Some useful workaround would be to specify false positives in _vld.ini_ that would be ignored. Something like:
```
IgnoreFalsePositives = "!type_info::name ", "something else"
```
Thanks