|
From: Julian S. <js...@ac...> - 2007-01-02 23:22:30
|
> Another suggestion is to prune the instances of valgrind until the problem > goes away. Omit applying valgrind at the outermost level, and/or at the > innermost level (replace the innermost level by a shell script that invokes > the original innermost executable without calling valgrind), etc. Also worth trying --tool=none just in case it's something specific just in case it's something specific to cachegrind/callgrind. I doubt it is, but still .. J |