Memory Management Debugger

Edit Package valgrind

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.

Refresh
Refresh
Source Files (show unmerged sources)
Filename Size Changed
armv6-support.diff 0000000302 302 Bytes
epoll-wait-fix.patch 0000001139 1.11 KB
jit-register-unregister.diff 0000007321 7.15 KB
valgrind-3.13.0.tar.bz2 0014723076 14 MB
valgrind.changes 0000036548 35.7 KB
valgrind.spec 0000009753 9.52 KB
valgrind.xen.patch 0000060563 59.1 KB
Latest Revision
Ludwig Nussel's avatar Ludwig Nussel (lnussel_factory) committed (revision 2)
fix links
Comments 0
openSUSE Build Service is sponsored by