Memory Management Debugger
Valgrind checks all memory operations in an application, like read,
write, malloc, new, free, and delete. Valgrind can find uses of
uninitialized memory, access to already freed memory, overflows,
illegal stack operations, memory leaks, and any illegal
new/malloc/free/delete commands. Another program in the package is
"cachegrind," a profiler based on the valgrind engine.
To use valgrind you should compile your application with "-g -O0"
compiler options. Afterwards you can use it with:
valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes
--db-attach=yes my_application, for example.
More valgrind options can be listed via "valgrind --help". There is
also complete documentation in the /usr/share/doc/packages/valgrind/
directory. A debugged application runs slower and needs much more
memory, but is usually still usable. Valgrind is still in development,
but it has been successfully used to optimize several KDE applications.
|_multibuild||0000000063 63 Bytes||about 2 years|
|armv6-support.diff||0000000213 213 Bytes||over 1 year|
|dhat-use-datadir.patch||0000000488 488 Bytes||8 months|
|parallel-lto.patch||0000001290 1.26 KB||over 1 year|
|valgrind-3.18.1.tar.bz2||0016149159 15.4 MB||19 days|
|valgrind.changes||0000052851 51.6 KB||19 days|
|valgrind.spec||0000012947 12.6 KB||19 days|
|valgrind.xen.patch||0000110497 108 KB||over 1 year|