Gentoo Packages

Search

Install

Install this package:

emerge -a dev-debug/valgrind

If the package is masked, you can unmask it using the autounmask tool or standard emerge options:

autounmask dev-debug/valgrind

Or alternatively:

emerge --autounmask-write -a dev-debug/valgrind

Package Information

Description:: Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as - Use of uninitialised memory - Reading/writing memory after it has been free'd - Reading/writing off the end of malloc'd blocks - Reading/writing inappropriate areas on the stack - Memory leaks -- where pointers to malloc'd blocks are lost forever - Passing of uninitialised and/or unaddressible memory to system calls - Mismatched use of malloc/new/new [] vs free/delete/delete [] - Some abuses of the POSIX Pthreads API
Homepage:: https://www.valgrind.org
License:: GPL-2

Versions

Version	EAPI	Keywords	Slot
9999	7	-* ~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x64-solaris	0

Metadata

Description

Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as - Use of uninitialised memory - Reading/writing memory after it has been free'd - Reading/writing off the end of malloc'd blocks - Reading/writing inappropriate areas on the stack - Memory leaks -- where pointers to malloc'd blocks are lost forever - Passing of uninitialised and/or unaddressible memory to system calls - Mismatched use of malloc/new/new [] vs free/delete/delete [] - Some abuses of the POSIX Pthreads API

Maintainers

Anthony G. Basile (blueness@gentoo.org) - Type: person

Raw Metadata XML

<pkgmetadata>
	<maintainer type="person">
		<email>blueness@gentoo.org</email>
		<name>Anthony G. Basile</name>
	</maintainer>
	<longdescription>
		Valgrind is a GPL'd tool to help you find memory-management problems
		in your programs. When a program is run under Valgrind's supervision,
		all reads and writes of memory are checked, and calls to
		malloc/new/free/delete are intercepted. As a result, Valgrind can
		detect problems such as

		- Use of uninitialised memory
		- Reading/writing memory after it has been free'd
		- Reading/writing off the end of malloc'd blocks
		- Reading/writing inappropriate areas on the stack
		- Memory leaks -- where pointers to malloc'd blocks are lost forever
		- Passing of uninitialised and/or unaddressible memory to system calls
		- Mismatched use of malloc/new/new [] vs free/delete/delete []
		- Some abuses of the POSIX Pthreads API
	</longdescription>
</pkgmetadata>

Lint Warnings

[Warning] USE flag 'mpi' in ebuild 9999 is not documented in metadata.xml
[Error] Missing md5-cache for ebuild valgrind-9999
[Error] Missing or unparsable Manifest file

USE Flags

Manage flags for this package: euse -i <flag> -p dev-debug/valgrind | euse -E <flag> -p dev-debug/valgrind | euse -D <flag> -p dev-debug/valgrind

Flag	Description	9999
mpi	⚠️	✓

Files

valgrind-3.15.0-Build-ldst_multiple-test-with-fno-pie.patch
valgrind-3.7.0-respect-flags.patch

dev-debug/valgrind (riscv)