Dr. Memory internal crash at PC 0x5ece6246

_From [mschos...@gmail.com](https://code.google.com/u/104903301621099697456/) on November 17, 2014 16:29:32_

~~Dr.M~~ WARNING: application exited with abnormal code 0xffffffff What steps will reproduce the problem? This error occurs when my application (datacast.exe) returns with 0. I recently updated to version 1.8.0 of drmemory from (I think) version 1.6. I didn't have this issue with version 1.6, but my application has also changed since. Previously when I used drmemory 1.6, my application used a static build of a pthreads API ( https://www.sourceware.org/pthreads-win32/ ). Now I am using their pre-built dynamic version of the pthreads api library because I was having issues with my build of their library. I don't know if the use of this library could be a contributor to this issue? What is the expected output? What do you see instead? What version of the product are you using? On what operating system? 1.8.0

Does the problem go away when running in light mode (pass "-light" to Dr.
Memory)? What about when running with the options "-leaks_only
-no_count_leaks -no_track_allocs"?

When using -light, problem goes away.
When using -leaks_only, problem goes away.
When using -no_count_leaks, problem persists.
when using -no_track_allocs, problem goes away. Does the problem go away when using the most recent build from http://build.chromium.org/p/client.drmemory/builds/? Try the debug version of Dr. Memory and of its underlying engine DynamoRIO by passing "-debug -dr_debug -pause_at_assert" to drmemory.exe. Are any messages reported? Please provide any additional information below. Please also see the "Narrowing Down the Source of the Problem" section of https://code.google.com/p/drmemory/wiki/Debugging .

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=1657_