I develop a C++ DLL with Visual Studio 2017 and I have some memory issues. I would like to use Application Verifier to debug it but the application who runs my DLL (a third-party application) is also heap corrupted. So if I activate Application Verifier, the application crashes before my DLL is loaded.
Is it possible to say to Application Verifier to only take care of heap corruption of a DLL or a module? If not, is there a way to debug my DLL with another tool?
Why not write a simple wrapper app? I've had to do that for a third party DLL that caused heap corruptions that would later crash our app. In this case it was in the destructor so I only had to load and free it. But if that didn't find it for you you could add unit tests for each export.