Using Microsoft Visual Studio 2010 10.0.40219.1 SP1Rel
Running Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01
Using Microsoft Visual C++ 2010 x86 Runtime 10.0.40219
Using Windows SDK 7.1.7600.0.30514
Targeting x86 with the Debug profile
Depends shows no missing dependencies.
Running the application yields a crash with the attached callstack.
If I rebuild the project and use the replacement DLL built in Debug, I can get:
Visual Leak Detector read settings from file: C:\Program Files (x86)\Visual Leak Detector\vld.ini
...to dump to the console, but I get a crash using std::string when it calls msvcr100d.dll!memcpy.
If I rebuild the project and use the replacement DLL built in Release, no console output is used. The application crashes inside of std::tree.
Using Depends on either of the newly generated DLL yields:
Error: The Side-by-Side configuration information for "c:\program files (x86)\visual leak detector\src\win32\debug\VLD_X86.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
My colleague was able to get Visual Leak Detector to work a while back with this project. However, I doubt he was using the latest C++ compiler, Visual C++ runtime, and Windows SDK.
Does anyone have any ideas on how to resolve this?
Thank you,
Jason Stern
Comments: > The DLL itself seems to be sprinkled liberally throughout my PC. The System32 and SysWOW64 version is 6.1.7601.17514. We use different version, copy dbghelp.dll and manifest from VLD folder.
Running Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01
Using Microsoft Visual C++ 2010 x86 Runtime 10.0.40219
Using Windows SDK 7.1.7600.0.30514
Targeting x86 with the Debug profile
Depends shows no missing dependencies.
Running the application yields a crash with the attached callstack.
If I rebuild the project and use the replacement DLL built in Debug, I can get:
Visual Leak Detector read settings from file: C:\Program Files (x86)\Visual Leak Detector\vld.ini
...to dump to the console, but I get a crash using std::string when it calls msvcr100d.dll!memcpy.
If I rebuild the project and use the replacement DLL built in Release, no console output is used. The application crashes inside of std::tree.
Using Depends on either of the newly generated DLL yields:
Error: The Side-by-Side configuration information for "c:\program files (x86)\visual leak detector\src\win32\debug\VLD_X86.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
My colleague was able to get Visual Leak Detector to work a while back with this project. However, I doubt he was using the latest C++ compiler, Visual C++ runtime, and Windows SDK.
Does anyone have any ideas on how to resolve this?
Thank you,
Jason Stern
Comments: > The DLL itself seems to be sprinkled liberally throughout my PC. The System32 and SysWOW64 version is 6.1.7601.17514. We use different version, copy dbghelp.dll and manifest from VLD folder.