Hello,
I'm using VLD to check a big project for memory leaks, the project consists of an executable and a bunch of other libraries in dll form.
I'm writing a new library, called A, which is loaded on run time by the exe, it also uses functions from a second library, called B.
The library B is very old, buggy with a lot of memory leaks.
When I add vld.h to my library, A, it will also trace the leaks originating from the library B.
How can I use/configure VLD to only trace the memory leaks from library A and ignore those originating from library B
Thanks,
Comments: You should be able to use VLDDisable prior to calls to library B and then reactivate VLD leak detection after the call with VLDEnable. Documentation is here [Controlling Leak Detection at Runtime](https://vld.codeplex.com/wikipage?title=Controlling%20Leak%20Detection%20at%20Runtime&referringTitle=Documentation)
I'm using VLD to check a big project for memory leaks, the project consists of an executable and a bunch of other libraries in dll form.
I'm writing a new library, called A, which is loaded on run time by the exe, it also uses functions from a second library, called B.
The library B is very old, buggy with a lot of memory leaks.
When I add vld.h to my library, A, it will also trace the leaks originating from the library B.
How can I use/configure VLD to only trace the memory leaks from library A and ignore those originating from library B
Thanks,
Comments: You should be able to use VLDDisable prior to calls to library B and then reactivate VLD leak detection after the call with VLDEnable. Documentation is here [Controlling Leak Detection at Runtime](https://vld.codeplex.com/wikipage?title=Controlling%20Leak%20Detection%20at%20Runtime&referringTitle=Documentation)