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
VEX-x86-nop-pattern.patch 0000005430 5.3 KB
VEX-x86-pinsrd.patch 0000002575 2.51 KB
_multibuild 0000000063 63 Bytes
armv6-support.diff 0000000213 213 Bytes
dhat-use-datadir.patch 0000000488 488 Bytes
parallel-lto.patch 0000001365 1.33 KB
valgrind-3.22.0.tar.bz2 0016565502 15.8 MB
valgrind.changes 0000062320 60.9 KB
valgrind.spec 0000013540 13.2 KB
valgrind.xen.patch 0000110497 108 KB
Latest Revision
Stephan Kulow's avatar Stephan Kulow (coolo) committed (revision 2)
Comments 1

Bernhard Wiedemann's avatar

GOOD: reproducibleopensuse scripts found this valgrind to have "status" : "reproducible"

openSUSE Build Service is sponsored by