On Thu, Apr 30, 2009 at 7:37 PM, daniel.delg...@interactivedata.com wrote:
Thusfar the helgrind reports have gone away each of the times I ran this
application
without dlmalloc.
Are you familiar with the VALGRIND_MALLOCLIKE_BLOCK() and
VALGRIND_FREELIKE_BLOCK() macro's defined in the header
Thusfar the helgrind reports have gone away each of the times I ran this
application without dlmalloc. It IS a race condition and while I was able
to run it 3-4 times without report that's only 1-2 more times than the
cases where I get one report in 1-2 run. The time it takes to do the
minimal
Hello all,
This is my first post. I am using Valgrind 3.4.1. The application I was
testing for what seems to be memory corruption is compiled along with
dlmalloc-2.8.3.c
Has anyone had experience with this? Will I be seeing false positives?
If I recall, I had used this in a past (3.1?)
To
Daniel Delgado/comst...@spc
cc
valgrind-users@lists.sourceforge.net
Subject
Re: [Valgrind-users] dlmalloc and helgrind (drd?) ?
Neither of these tools understand custom malloc functions.
But it's easy to tech them.
Way1: hack the dlmalloc code to include helgrind's client requests
(see helgrind.h
