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
I need to run an opengl and mpi program remotely - with valgrind.
I'm attempting to run a command like so:
LD_PRELOAD=$prefix/lib/valgrind/amd64-linux/libmpiwrap.so mpirun -np
$i $prefix/bin/valgrind vglrun ./test
While this gives a lot of output, and the program runs successfully, I
don't see
I was wondering what it takes to be able to install a pre-built Valgrind to a
location other than what was specified with the --prefix at build time. I
did a lot of searching, but didn't turn up much except for some references to a
VALGRIND_LIB variable. I'd like to know the steps involved
