Linux workstation

Upstream software project

valgrind

Tool to help find memory-management problems in programs (development files)

About valgrind

Tool to help find memory-management problems in programs (development files)

This project links 24 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Alpine Linux 3.21: 4 package records; Alpine Linux 3.22: 4 package records; Alpine Linux 3.23: 4 package records; openSUSE Leap 15.6: 4 package records; openSUSE Leap 16.0: 4 package records; openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.valgrind: recorded package coverageAlpine Linux 3.214 recordsAlpine Linux 3.224 recordsAlpine Linux 3.234 recordsopenSUSE Leap 15.64 recordsopenSUSE Leap 16.04 recordsopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
valgrind
Publisher
Not authoritatively mapped
Native package records
24
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Metadata completeness
70/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Alpine Linux 3.21

  1. valgrind

    Alpine Linux 3.21 / source valgrind

    3.24.0-r0

    Tool to help find memory-management problems in programs

    aarch64x86_64v3.21
  2. valgrind-dev

    Alpine Linux 3.21 / source valgrind

    3.24.0-r0

    Tool to help find memory-management problems in programs (development files)

    aarch64x86_64v3.21
  3. valgrind-doc

    Alpine Linux 3.21 / source valgrind

    3.24.0-r0

    Tool to help find memory-management problems in programs (documentation)

    aarch64x86_64v3.21
  4. valgrind-scripts

    Alpine Linux 3.21 / source valgrind

    3.24.0-r0

    Tool to help find memory-management problems in programs (perl+python cachegrind/callgrind script tools)

    aarch64x86_64v3.21

Alpine Linux 3.22

  1. valgrind

    Alpine Linux 3.22 / source valgrind

    3.25.1-r1

    Tool to help find memory-management problems in programs

    aarch64x86_64v3.22
  2. valgrind-dev

    Alpine Linux 3.22 / source valgrind

    3.25.1-r1

    Tool to help find memory-management problems in programs (development files)

    aarch64x86_64v3.22
  3. valgrind-doc

    Alpine Linux 3.22 / source valgrind

    3.25.1-r1

    Tool to help find memory-management problems in programs (documentation)

    aarch64x86_64v3.22
  4. valgrind-scripts

    Alpine Linux 3.22 / source valgrind

    3.25.1-r1

    Tool to help find memory-management problems in programs (perl+python cachegrind/callgrind script tools)

    aarch64x86_64v3.22

Alpine Linux 3.23

  1. valgrind

    Alpine Linux 3.23 / source valgrind

    3.25.1-r2

    Tool to help find memory-management problems in programs

    aarch64x86_64v3.23
  2. valgrind-dev

    Alpine Linux 3.23 / source valgrind

    3.25.1-r2

    Tool to help find memory-management problems in programs (development files)

    aarch64x86_64v3.23
  3. valgrind-doc

    Alpine Linux 3.23 / source valgrind

    3.25.1-r2

    Tool to help find memory-management problems in programs (documentation)

    aarch64x86_64v3.23
  4. valgrind-scripts

    Alpine Linux 3.23 / source valgrind

    3.25.1-r2

    Tool to help find memory-management problems in programs (perl+python cachegrind/callgrind script tools)

    aarch64x86_64v3.23

openSUSE Leap 15.6

  1. valgrind

    openSUSE Leap 15.6 / Development/Tools/Debuggers / source valgrind

    3.22.0-150600.1.3

    Memory Management Debugger

    aarch64ppc64les390xx86_64leap-15.6
  2. valgrind-32bit

    openSUSE Leap 15.6 / Development/Tools/Debuggers / source valgrind

    3.22.0-150600.1.3

    Memory Management Debugger

    s390xx86_64leap-15.6
  3. valgrind-client-headers

    openSUSE Leap 15.6 / Development/Tools/Debuggers / source valgrind-client-headers-source

    3.22.0-150600.1.2

    Header files for for Valgrind

    noarchleap-15.6
  4. valgrind-devel

    openSUSE Leap 15.6 / Development/Tools/Debuggers / source valgrind

    3.22.0-150600.1.3

    Header files for for Valgrind

    aarch64ppc64les390xx86_64leap-15.6

openSUSE Leap 16.0

  1. valgrind

    openSUSE Leap 16.0 / Development/Tools/Debuggers / source valgrind

    3.24.0-160000.2.2

    Memory Management Debugger

    aarch64ppc64les390xx86_64leap-16.0
  2. valgrind-32bit

    openSUSE Leap 16.0 / Development/Tools/Debuggers / source valgrind

    3.25.1-160000.1.1

    Memory Management Debugger

    s390xx86_64leap-16.0
  3. valgrind-client-headers

    openSUSE Leap 16.0 / Development/Tools/Debuggers / source valgrind-client-headers-source

    3.27.1-160000.1.1

    Header files for for Valgrind

    noarchleap-16.0
  4. valgrind-devel

    openSUSE Leap 16.0 / Development/Tools/Debuggers / source valgrind

    3.24.0-160000.2.2

    Header files for for Valgrind

    aarch64ppc64les390xx86_64leap-16.0

openSUSE Tumbleweed

  1. valgrind

    openSUSE Tumbleweed / Development/Tools/Debuggers / source valgrind

    3.27.1-1.3

    Memory Management Debugger

    x86_64tumbleweed
  2. valgrind-32bit

    openSUSE Tumbleweed / Development/Tools/Debuggers / source valgrind

    3.27.1-1.3

    Memory Management Debugger

    x86_64tumbleweed
  3. valgrind-client-headers

    openSUSE Tumbleweed / Development/Tools/Debuggers / source valgrind-client-headers-source

    3.27.1-1.2

    Header files for for Valgrind

    noarchtumbleweed
  4. valgrind-devel

    openSUSE Tumbleweed / Development/Tools/Debuggers / source valgrind

    3.27.1-1.3

    Header files for for Valgrind

    x86_64tumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.