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.
- Developed at devel:tools
- Sources inherited from project openSUSE:Factory
-
5
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/valgrind && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| 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 | 0000062017 60.6 KB | |
| valgrind.spec | 0000013359 13 KB | |
| valgrind.xen.patch | 0000110497 108 KB |
Revision 149 (latest revision is 151)
Ana Guerrero (anag+factory)
accepted
request 1128515
from
Dirk Mueller (dirkmueller)
(revision 149)
- update to 3.22.0: (jsc#PED-5442):
* Memcheck now tests and warns about the values used for
alignment and size. These apply to various functions: memalign,
posix_memalign and aligned_alloc in C and various overloads
of operators new and delete in C++. The kinds of error that can
be detected are
- invalid alignment, for instance the alignment is usually required
to be a power of 2
- mismatched alignment between aligned allocation and aligned
deallocation
- mismatched size when sized delete is used
- bad size for functions that have implementation defined behaviour
when the requested size is zero
* many bug fixes, see https://valgrind.org/docs/manual/dist.news.html
Comments 1
Version 3.15.0 is latest stable