vld v2.4rc2
In VS2013 if I add
#include <vld.h>
the unit tests crash if run.
This is the output:
```
------ Run test started ------
The active Test Run was aborted because the execution process exited unexpectedly. Check the execution process logs for more information. If the logs are not enabled, then enable the logs and try again.
========== Run test finished: 0 run (0:00:00,8760876) ==========
```
If run in debug mode I get this error:
```
Unhandled exception at 0x77CA8E19 (ntdll.dll) in vstest.executionengine.x86.exe: 0xC0000005: Access violation writing location 0x00000014.
```
and this call stack:
```
> ntdll.dll!_RtlpWaitOnCriticalSection@8() Unknown
ntdll.dll!_RtlEnterCriticalSection@4() Unknown
vld_x86.dll!0d24ea8b() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for vld_x86.dll]
vld_x86.dll!0d24b43d() Unknown
dbghelp.dll!0d2acd40() Unknown
dbghelp.dll!0d2ae7da() Unknown
dbghelp.dll!0d2acc26() Unknown
dbghelp.dll!0d2eb311() Unknown
[External Code]
Nvd3d9wrap.dll!73563da3() Unknown
Microsoft.VisualStudio.TestTools.CppUnitTestFramework.Executor.dll!0f3c6ac6() Unknown
[External Code]
```
Please note that vld is working correctly in this project. Just the unit tests have this problem.
Comments: Further to my previous post, I have found a workaround: 1) In VS select your UnitTest project and build in debug 2) Open the Developer Command Prompt for VS2013 3) Navigate to your UnitTest Debug folder 4) Type the command: vstest.console.exe /platform:x86 [YourUnitTestName].dll 5) Your unit test should run to completion. You will see multiple "Visual Leak Detector: Waiting for threads to terminate..." Allow this to continue, eventually it will terminate and you will get your VLD report, without the Access Violation errors.
In VS2013 if I add
#include <vld.h>
the unit tests crash if run.
This is the output:
```
------ Run test started ------
The active Test Run was aborted because the execution process exited unexpectedly. Check the execution process logs for more information. If the logs are not enabled, then enable the logs and try again.
========== Run test finished: 0 run (0:00:00,8760876) ==========
```
If run in debug mode I get this error:
```
Unhandled exception at 0x77CA8E19 (ntdll.dll) in vstest.executionengine.x86.exe: 0xC0000005: Access violation writing location 0x00000014.
```
and this call stack:
```
> ntdll.dll!_RtlpWaitOnCriticalSection@8() Unknown
ntdll.dll!_RtlEnterCriticalSection@4() Unknown
vld_x86.dll!0d24ea8b() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for vld_x86.dll]
vld_x86.dll!0d24b43d() Unknown
dbghelp.dll!0d2acd40() Unknown
dbghelp.dll!0d2ae7da() Unknown
dbghelp.dll!0d2acc26() Unknown
dbghelp.dll!0d2eb311() Unknown
[External Code]
Nvd3d9wrap.dll!73563da3() Unknown
Microsoft.VisualStudio.TestTools.CppUnitTestFramework.Executor.dll!0f3c6ac6() Unknown
[External Code]
```
Please note that vld is working correctly in this project. Just the unit tests have this problem.
Comments: Further to my previous post, I have found a workaround: 1) In VS select your UnitTest project and build in debug 2) Open the Developer Command Prompt for VS2013 3) Navigate to your UnitTest Debug folder 4) Type the command: vstest.console.exe /platform:x86 [YourUnitTestName].dll 5) Your unit test should run to completion. You will see multiple "Visual Leak Detector: Waiting for threads to terminate..." Allow this to continue, eventually it will terminate and you will get your VLD report, without the Access Violation errors.