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.

Source Files
Filename Size Changed Actions
0001-Accept-read-only-PT_LOAD-segments-and-.rodata.patch 0000004239 4.14 KB about 1 year
Fix-access-to-time-base-register-to-return-64-bits.patch 0000005192 5.07 KB about 1 year
Implement-emulated-system-registers.-Fixes-392146.patch 0000013834 13.5 KB about 1 year
armv6-support.diff 0000000302 302 Bytes about 1 year
epoll-wait-fix.patch 0000001139 1.11 KB about 1 year
jit-register-unregister.diff 0000007321 7.15 KB about 1 year
valgrind-3.13.0.tar.bz2 0014723076 14 MB about 1 year
valgrind.changes 0000037684 36.8 KB about 1 year
valgrind.spec 0000010062 9.83 KB about 1 year
valgrind.xen.patch 0000061769 60.3 KB about 1 year
Comments for valgrind.9221 0