On Wednesday 11 January 2006 17:18, David Faure wrote:
> > I am sure it would but I don't know how to use valgrind for debugging. It
> > has so many tools and flags I don't even know where to start. Just using
> > it without flags and parameters doesn't show anything.
> > There is nothing in the FAQ about it and google doesn't give me hints
> > either.
>
> valgrind --tool=memcheck --num-callers=50 kmyapp
>
> With some versions of valgrind it's "skin" instead of "tool".

Be sure to build the app with --enable-debug=full and sometimes you have to
use the --nofork option. I valgrind kttsd like this:

valgrind --tool=memcheck --leak-check=yes --num-callers=16
--log-file=valgrind.log kttsd --nofork

--
Gary Cramblitt (aka PhantomsDad)

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<