macOS
brew install valgrindlocal Homebrew formula metadata
sudo port install valgrindMacPorts ports tree · devel/valgrind/Portfile · Quelle: api.github.com
brew / Rang 1640
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für valgrind in AI-Agent-Workflows.
Installation
brew install valgrindlocal Homebrew formula metadata
sudo port install valgrindMacPorts ports tree · devel/valgrind/Portfile · Quelle: api.github.com
sudo apk add valgrindAlpine Linux edge package indexes · valgrind · Quelle: dl-cdn.alpinelinux.org
sudo apt install valgrindDebian stable package indexes · valgrind · Quelle: deb.debian.org
sudo dnf install valgrindFedora Rawhide package metadata · valgrind · Quelle: dl.fedoraproject.org
nix profile install nixpkgs#valgrindnixpkgs package indexes · pkgs/by-name/va/valgrind/package.nix · Quelle: api.github.com
sudo pacman -S valgrindArch Linux sync databases · valgrind · Quelle: geo.mirror.pkgbuild.com
sudo zypper install valgrindopenSUSE Tumbleweed package metadata · valgrind · Quelle: download.opensuse.org
Überblick
Dynamic analysis tools (memory, debug, profiling)
Verlauf
Valgrind began as Julian Seward's attempt to build an open source memory-checking tool for x86/Linux in the spirit of Purify, but without source rewriting or relinking. Nicholas Nethercote's twentieth-anniversary retrospective places the first 1.0 release in July 2002, after early use by KDE developers, and notes that Cachegrind was committed in April 2002. Soon afterward the project split its generic dynamic-binary-instrumentation engine from individual analysis tools: the original memory checker became Memcheck, while Valgrind became the overall framework.
That split shaped Valgrind's long-term role. The official manual describes it as an instrumentation framework with standard tools including Memcheck for C/C++ memory errors, Cachegrind and Callgrind for cache/call profiling, Helgrind and DRD for thread errors, Massif and DHAT for heap profiling, plus smaller developer and research tools. This made Valgrind both a daily debugging command and a platform for building heavyweight dynamic-analysis experiments.
The project also became influential research and infrastructure. Nethercote records papers on Memcheck's bit-precise undefined-value tracking and Valgrind's heavyweight instrumentation architecture, and notes that later tools such as AddressSanitizer were inspired by Memcheck while making different speed/coverage tradeoffs. By the 2010s Seward and Nethercote had moved into emeritus roles, with many other contributors and Mark Wielaard as lead maintainer, but Valgrind remained a reference tool for deep user-space dynamic analysis.
Adoption followed the places where native-code correctness bugs are expensive: C and C++ applications, libraries, language runtimes, databases, browsers, scientific programs, embedded software, and automated regression suites. The Valgrind site emphasizes that it works on existing binaries without recompilation and that it has been used on projects ranging from personal code to very large codebases. Its standard package-nerd usage remains direct and boring: compile with debug symbols, run a program under `valgrind` or a selected `--tool`, inspect source-mapped diagnostics, and, for CI or release checks, fail builds on leaks, invalid accesses, or concurrency issues.
Adoption followed the places where native-code correctness bugs are expensive: C and C++ applications, libraries, language runtimes, databases, browsers, scientific programs, embedded software, and automated regression suites. The Valgrind site emphasizes that it works on existing binaries without recompilation and that it has been used on projects ranging from personal code to very large codebases. Its standard package-nerd usage remains direct and boring: compile with debug symbols, run a program under `valgrind` or a selected `--tool`, inspect source-mapped diagnostics, and, for CI or release checks, fail builds on leaks, invalid accesses, or concurrency issues.
Sicherheitslage
Für valgrind wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
callgrind_annotate | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
callgrind_control | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
cg_annotate | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
cg_diff | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
cg_merge | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
ms_print | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
valgrind | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
valgrind-di-server | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
valgrind-listener | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
vgdb | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
vgstack | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Installationsmetadaten
| Paketschlüssel | brew:valgrind |
|---|---|
| Version | 3.27.1 |
| Paketmanager | Homebrew |
| Homepage | https://www.valgrind.org/ |
| Zuletzt aktualisiert | 2026-05-20T16:57:52Z |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
valgrind 1:3.24.0-3
instrumentation framework for building dynamic analysis tools
sudo apt install valgrindvalgrind-mpi 1:3.24.0-3
instrumentation framework for building dynamic analysis tools (MPI module)
sudo apt install valgrind-mpivalgrind
nix profile install nixpkgs#valgrindvalgrind 1:3.22.0-0ubuntu3
instrumentation framework for building dynamic analysis tools
sudo apt install valgrindvalgrind-mpi 1:3.22.0-0ubuntu3
instrumentation framework for building dynamic analysis tools (MPI module)
sudo apt install valgrind-mpivalgrind 3.25.1-r2
Tool to help find memory-management problems in programs
sudo apk add valgrindvalgrind-dev 3.25.1-r2
Tool to help find memory-management problems in programs (development files)
sudo apk add valgrind-devvalgrind-doc 3.25.1-r2
Tool to help find memory-management problems in programs (documentation)
sudo apk add valgrind-docvalgrind-scripts 3.25.1-r2
Tool to help find memory-management problems in programs (perl+python cachegrind/callgrind script tools)
sudo apk add valgrind-scriptsvalgrind 3.27.1-2.fc45
Dynamic analysis tools to detect memory or thread bugs and profile
sudo dnf install valgrindvalgrind-devel 3.27.1-2.fc45
Development files for valgrind aware programs
sudo dnf install valgrind-develvalgrind-docs 3.27.1-2.fc45
Documentation for valgrind tools, scripts and gdb integration
sudo dnf install valgrind-docsvalgrind-gdb 3.27.1-2.fc45
Tools for integrating valgrind and gdb
sudo dnf install valgrind-gdbvalgrind-openmpi 3.27.1-2.fc45
OpenMPI support for valgrind
sudo dnf install valgrind-openmpivalgrind-scripts 3.27.1-2.fc45
Scripts for post-processing valgrind tool output
sudo dnf install valgrind-scriptsvalgrind-tools-devel 3.27.1-2.fc45
Development files for building valgrind tools.
sudo dnf install valgrind-tools-develQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.