DynamoRIO / DynamoRIO/drmemory
DrMemory failure with VS2015 Update 3
- Dominant language
- C
- Stars
- 2.7k
- Forks
- 290
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've been using DrMemory for 6 months to run dynamic code analysis on a software I'm contributing to. Things went great until we installed update 3 of Visual Studio 2015.
With update 3 of VS2015, I started having application crash because of an **illegal memory access** fault (code `0xc0000005`). I have the error only when I run DrMemory with the release builds (I mainly use x86-release build). Here is an example of epilogue of DrMemory log:
```
~~Dr.M~~ 33 potential error(s) (suspected false positives)
~~Dr.M~~ (details: C:\DrMemory-1.11.2\drmemory\logs\DrMemory-UnitTests.exe.10068.001\potential_errors.txt)
~~Dr.M~~ 2 potential leak(s) (suspected false positives)
~~Dr.M~~ (details: C:\DrMemory-1.11.2\drmemory\logs\DrMemory-UnitTests.exe.10068.001\potential_errors.txt)
~~Dr.M~~ 0 user-suppressed, 0 default-suppressed error(s)
~~Dr.M~~ 1 user-suppressed, 1 default-suppressed leak(s)
~~Dr.M~~ 240 unique, 476 total, 49852 byte(s) of still-reachable allocation(s)
~~Dr.M~~ (re-run with "-show_reachable" for details)
~~Dr.M~~ Details: C:\DrMemory-1.11.2\drmemory\logs\DrMemory-UnitTests.exe.10068.001\results.txt
~~Dr.M~~ WARNING: application exited with abnormal code 0xc0000005
```
I do not observe this error when running x86-release build alone (without drmemory). And I do not observe any error when running DrMemory with the x86-debug build.
I've tried to follow guidance from [Debugging DrMemory page](https://github.com/DynamoRIO/drmemory/wiki/Debugging), especially "Narrowing Down the Source of Problem" section, but didn't have any significant change except when using options `-leaks_only -no_count_leaks -no_track_allocs`. The issue seems to be skipped, but Dr.Memory crashes later:

I was using `drmemory-1.10.1`, but also tried versions `1.9.4` and `1.11.2`. They all behave the same regarding this issue.
I think the issue is related to the recent Visual Studio update (.net core/crt?). But I'm not sure whether DrMemory is implicated in this failure.
Thanks
Marouane
Contributor guide
Assessment
This issue has not been assessed yet.