OK - I was going to say mea cupla and apologise for missing this in the documentation but then I looked and I couldn't find any reference to this action in this or anywhere else on your project site except for a recent user, 123456, who said 4 days ago - quote: I was getting the error 0xc0150002, copying the files dbghelp.dll and Microsoft.DTfW.DHL.manifest from the dbghelp folder to the bin folder solved the problem.
However, I followed your instructions above and copied these two files to the folder containing my executable and it did not solve the problem!
I then did what the user 123456 did, i.e. copy these 2 files to the "C:\Program Files (x86)\Visual Leak Detector\bin\Win32" folder rather than the executable's folder and it solved the problem.
This raises the question - why not install them there in the first place (and the x64 version into the corresponding folder)?
As I assume this only works because I selected to add the VLD bin directories to my path during installation, I removed them from my path and VLD only works if I copy those 2 files and vld_386.dll to the folder containing the executable.
So, it seems that VLD works as follows:
I assume this is largely due to Microsoft's DLL Hell implementation.
As I have built only a x86 version of my program, I haven't researched placing the x64 versions of dbghelp.dll and Microsoft.DTfW.DHL.manifest in the x64 VLD bin folders and the impact of having the x86 bin folders before the x64 bin folders in the PATH statement.
However, I followed your instructions above and copied these two files to the folder containing my executable and it did not solve the problem!
I then did what the user 123456 did, i.e. copy these 2 files to the "C:\Program Files (x86)\Visual Leak Detector\bin\Win32" folder rather than the executable's folder and it solved the problem.
This raises the question - why not install them there in the first place (and the x64 version into the corresponding folder)?
As I assume this only works because I selected to add the VLD bin directories to my path during installation, I removed them from my path and VLD only works if I copy those 2 files and vld_386.dll to the folder containing the executable.
So, it seems that VLD works as follows:
- With VLD bin folders in the PATH, the two files dbghelp.dll and Microsoft.DTfW.DHL.manifest must be in the VLD bin folder i.e. the same folder as vld_x86.dll - "C:\Program Files (x86)\Visual Leak Detector\bin\Win32" (or vld_x64.dll in the x64 equivalent)
-
Without VLD bin folders in the PATH, the three files dbghelp.dll, Microsoft.DTfW.DHL.manifest and vld_x86.dll (or vld_x64.dll) must be in the executable's folder.
I assume this is largely due to Microsoft's DLL Hell implementation.
As I have built only a x86 version of my program, I haven't researched placing the x64 versions of dbghelp.dll and Microsoft.DTfW.DHL.manifest in the x64 VLD bin folders and the impact of having the x86 bin folders before the x64 bin folders in the PATH statement.