[Valgrind-users] valgrind running REALLY slow, then no output

[Jenny L. <jli...@pi...>]

Hello,

Hopefully someone can help me sort out this problem...

I used to be able to run valgrind on my program in a reasonable time =
period - 5 to 10 times slower than the program runs without it.  Then, =
some new code was introduced into the program.  After this, valgrind =
runs excruciatingly slow and when it finishes it claims "0 errors from 0 =
contexts" and "0 bytes lost in 0 blocks".  Before this new code was =
introduced, there were numerous errors reported by valgrind.

What I am running is a CppUnit test that isolates the newly introduced =
code.  When not under valgrind, the test completes in 4 seconds.  When =
running under valgrind it takes 13 minutes 54 seconds.  Into this test I =
intentionally created a string variable on the heap and never deleted =
it.  The valgrind output did catch this leak, but reported no memory =
errors - which I really don't believe.

Could this be because my program is doing something not supported by =
valgrind?
Any ideas for figuring out where it is getting hung up?

I am running the valgrind-20030716 with Red Hat kernel 2.4.20-18.8.  I =
compiled valgrind on this machine.

Thanks,
Jenny Lighthart