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
Filename Size Changed
0001-Add-newer-constants-for-prctl-syscall.patch 0000001959 1.91 KB
0001-Fix-makefile-consistency-check.patch 0000000922 922 Bytes
0001-s390x-Add-CPU-model-for-z15.patch 0000005582 5.45 KB
0001-s390x-Add-models-z14-and-z14-ZR1.patch 0000005205 5.08 KB
0001-s390x-Clean-up-s390-check-opcodes.pl.patch 0000001435 1.4 KB
0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch 0000001101 1.08 KB
_multibuild 0000000063 63 Bytes
armv6-support.diff 0000000302 302 Bytes
valgrind-3.15.0.tar.bz2 0020241437 19.3 MB
valgrind-client-headers-source.changes 0000046972 45.9 KB
valgrind.changes 0000047305 46.2 KB
valgrind.spec 0000012968 12.7 KB
valgrind.xen.patch 0000104761 102 KB
Latest Revision
Yuchen Lin's avatar Yuchen Lin (maxlin_factory) committed (revision 26)
update _link
Comments 0
openSUSE Build Service is sponsored by