Frequently Asked Questions

When I try to compile my program with VLD, it fails and the compiler gives this error: Cannot open include file: 'vld.h': No such file or directory.

The compiler can't find the header file that VLD installed. This probably means that VLD's include subdirectory has not been added to the Visual C{"++"} include search path. See the section above about Using Visual Leak Detector for instructions on how to add VLD's directories to the search path.

In the memory leak report, the callstack contains many lines that say "File and line number unvailable" or "Function name unavailable".

This may mean that VLD couldn't find the symbol database for your program. The symbol database is ususally in a file named my-program-name.pdb. If this file is not located in the same directory as the program itself, then VLD will probably not find it and can't show any file or function names. Set environment variable DBGHELP_DBGOUT to check this.

How can I see the call stack including file names and line numbers ? I can only see the address of call stack

Go into 'Project Settings->Linker->Debugging->Generate Debug Info' and change that setting to "Generate Debug Information optimized for sharing and publishing (/DEBUG:FULL)"

VLD crashes on output memory leaks with an Exception thrown at 0x7A047EAC (dbghelp.dll) in ... 0xC0000005

Go into 'Project Settings->Linker->Debugging->Generate Debug Info' and change that setting to "Generate Debug Information optimized for sharing and publishing (/DEBUG:FULL)"