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.
- Sources inherited from project SUSE:SLE-12-SP2:Update
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout SUSE:SLE-12-SP5:GA/valgrind.3987 && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
armv6-support.diff | 0000000302 302 Bytes | |
gcc5.patch | 0000001628 1.59 KB | |
jit-register-unregister.diff | 0000007321 7.15 KB | |
r15702.diff | 0000003038 2.97 KB | |
r15792.diff | 0000004183 4.08 KB | |
r15802.diff | 0000003595 3.51 KB | |
svn-r15766.patch | 0000005466 5.34 KB | |
valgrind-3.11.0.tar.bz2 | 0011910809 11.4 MB | |
valgrind.changes | 0000035159 34.3 KB | |
valgrind.spec | 0000009787 9.56 KB | |
vex-r3197.diff | 0000001163 1.14 KB | |
vex-r3210.diff | 0000002537 2.48 KB | |
vex-r3213.diff | 0000000958 958 Bytes |
Latest Revision
Release from SUSE:Maintenance:3987 / valgrind.SUSE_SLE-12-SP2_Update
Comments 0