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.
|armv6-support.diff||0000000187 187 Bytes||about 6 years|
|gcc-version.patch||0000000368 368 Bytes||almost 5 years|
|glibc-version.patch||0000001024 1 KB||over 4 years|
|jit-register-unregister.diff||0000007339 7.17 KB||almost 5 years|
|valgrind-3.10.1.tar.bz2||0010967905 10.5 MB||almost 5 years|
|valgrind-linux-4.0.patch||0000001079 1.05 KB||almost 5 years|
|valgrind.changes||0000033575 32.8 KB||over 4 years|
|valgrind.spec||0000009506 9.28 KB||almost 5 years|