Memory Management Debugger

Overview Repositories Revisions Requests Users Attributes Meta

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.

Download package
Checkout Package
osc -A https://api.opensuse.org checkout SUSE:SLE-15-SP1:GA/valgrind && cd $_
Create Badge

Build Results
RPM Lint

Refresh

Source Files

Filename	Size	Changed
0001-Bug-397187-s390x-Add-vector-register-support-for-vgd.patch	0000017709 17.3 KB	over 5 years ago
0001-Bug-400490-s390x-Fix-register-allocation-for-VRs-vs-.patch	0000003206 3.13 KB	over 5 years ago
0001-Bug-400491-s390x-Sign-extend-immediate-operand-of-LO.patch	0000001668 1.63 KB	over 5 years ago
0001-s390x-more-fixes.patch	0000002056 2.01 KB	over 5 years ago
Implement-emulated-system-registers.-Fixes-392146.patch	0000013912 13.6 KB	over 5 years ago
armv6-support.diff	0000000302 302 Bytes	over 5 years ago
jit-register-unregister.diff	0000007321 7.15 KB	over 8 years ago
valgrind-3.14.0.tar.bz2	0016602858 15.8 MB	over 5 years ago
valgrind.changes	0000040577 39.6 KB	over 5 years ago
valgrind.spec	0000010424 10.2 KB	over 5 years ago
valgrind.xen.patch	0000104761 102 KB	over 5 years ago

Revision 2 (latest revision is 6)

Stephan Kulow (coolo) committed over 5 years ago (revision 2)

- update valgrind.xen.patch to branch bug390553-20181125-ddfc274b2

- build against Toolchain module for SLE12
- add 0001-Bug-397187-s390x-Add-vector-register-support-for-vgd.patch
  0001-Bug-400490-s390x-Fix-register-allocation-for-VRs-vs-.patch,
  0001-Bug-400491-s390x-Sign-extend-immediate-operand-of-LO.patch,
  0001-s390x-more-fixes.patch,
  Implement-emulated-system-registers.-Fixes-392146.patch (FATE#326355)
- enable check (poo#36751)

- update to 3.14.0 (bsc#1114575, FATE#326355):
  see http://www.valgrind.org/docs/manual/dist.news.html
  * The new option --keep-debuginfo=no|yes (default no) can be used to retain
    debug info for unloaded code.  This allows saved stack traces (e.g. for
    memory leaks) to include file/line info for code that has been dlclose'd (or
    similar).  See the user manual for more information and known limitations.
  * Ability to specify suppressions based on source file name and line number.
  * Majorly overhauled register allocator.  No end-user changes, but the JIT
    generates code a bit more quickly now.
  * Preliminary support for macOS 10.13 has been added.
  * mips: support for MIPS32/MIPS64 Revision 6 has been added.
  * mips: support for MIPS SIMD architecture (MSA) has been added.
  * mips: support for MIPS N32 ABI has been added.
  * s390: partial support for vector instructions (integer and string) has been
    added.
  * Helgrind: Addition of a flag
    --delta-stacktrace=no|yes [yes on linux amd64/x86]
    which specifies how full history stack traces should be computed.
    Setting this to =yes can speed up Helgrind by 25% when using
    --history-level=full.

Places