[Valgrind-users] What to do when valgrind is too slow?

[jlh <jl...@gm...>]

Hello list!

A program I'm writing apparently has memory leaks that I'd like to
find.  However, the program has to process real time data and it
cannot process them fast enough when running in valgrind.  How
would one deal with this situation?  Ideally, I'd even like to run
it for a long time, like hours or even days, so that as many
different code paths as possible are being taken.

I once was under the -- perhaps mistaken -- impression that I
could re-compile the entire program with valgrind support
built-in, which would allow to find mem-leaks without the slow
down.  Is this possible or am I just badly mistaken about that?  I
couldn't find any information about it.  Would that make sense at
all?  I imagine that if I'm only interested in finding memory
leaks, it would be enough to instrument all calls to malloc(),
free(), etc. at compile (or link) time and then be able to run at
native speed, i.e. not using the CPU emulator.

This problem aside, I'm very happy with valgrind, as it helped me
fix some leaks already.

Thanks for any help.

Thanks,
jlh