Quantcast
Channel: Visual Leak Detector for Visual C++ 2008-2015
Viewing all articles
Browse latest Browse all 704

Commented Unassigned: VS2013: Unit tests crash [10568]

$
0
0
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: scrub the previous post, although the workaround appears to allow the unit tests to complete, VLD fails to detect any memory leaks present in unit tests.

Viewing all articles
Browse latest Browse all 704

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>