This project has moved and is read-only. For the latest updates, please go here.

VLD 2.4RC2 - SQLDriverConnect - locked...

Aug 5, 2015 at 10:23 PM
Hi,

First at all thank you for this amazing system to detect memory leak.
I am checking the 2.4RC2 with vs2013 express.

Do you know if there is any limitation with the ODBC API SQLDriverConnectA.


Thank you in advance
regards
Aug 11, 2015 at 3:28 PM
More info.

The SqlDriverConnectA method is wrapped into a function named connectSQL of a static lib.

When the connectSQL method is execute into a Thread : the process is locking
When the connectSQL method is execute directly : works fine but appear a lot of warning like


WARNING: Visual Leak Detector: Failed to unload the symbols for sqlsrv32.rll. Function names and line numbers shown in the memory leak report for sqlsrv32.rll may be inaccurate.

WARNING: Visual Leak Detector: A module, sqlsrv32.dll, included in memory leak detection
does not have any debugging symbols available, or they could not be located.
Function names and/or line numbers for this module may not be available.

WARNING: Visual Leak Detector: A module, dssenh.dll, included in memory leak detection
does not have any debugging symbols available, or they could not be located.
Function names and/or line numbers for this module may not be available.



Questions?
Anyone know if I have to include "vld.h" to the lib? or It´s a problem if the threads, odbc API ...