Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / valgrind / refs/tags/21.01.0-rel.0 / . / README
blob: 45f2917d3d03419b8284afd9663f4b75343bdf06 [file] [log] [blame]
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]1
nethercote5da1e172003-12-03 21:44:45 +0000[diff] [blame]2Release notes for Valgrind
3~~~~~~~~~~~~~~~~~~~~~~~~~~
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]4If you are building a binary package of Valgrind for distribution,
5please read README_PACKAGERS. It contains some important information.
sewardj365a8512002-07-01 08:30:05 +0000[diff] [blame]6
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]7If you are developing Valgrind, please read README_DEVELOPERS. It contains
8some useful information.
9
10For instructions on how to build/install, see the end of this file.
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]11
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]12If you have problems, consult the FAQ to see if there are workarounds.
13
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]14
15Executive Summary
16~~~~~~~~~~~~~~~~~
sewardje089f012010-10-13 21:47:29 +0000[diff] [blame]17Valgrind is a framework for building dynamic analysis tools. There are
18Valgrind tools that can automatically detect many memory management
19and threading bugs, and profile your programs in detail. You can also
20use Valgrind to build new tools.
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]21
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]22The Valgrind distribution currently includes six production-quality
sewardje089f012010-10-13 21:47:29 +0000[diff] [blame]23tools: a memory error detector, two thread error detectors, a cache
24and branch-prediction profiler, a call-graph generating cache abd
25branch-prediction profiler, and a heap profiler. It also includes
26three experimental tools: a heap/stack/global array overrun detector,
27a different kind of heap profiler, and a SimPoint basic block vector
njn57b87ea2009-07-14 04:24:18 +0000[diff] [blame]28generator.
nethercote5da1e172003-12-03 21:44:45 +0000[diff] [blame]29
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]30Valgrind is closely tied to details of the CPU, operating system and to
31a lesser extent, compiler and basic C libraries. This makes it difficult
32to make it portable. Nonetheless, it is available for the following
33platforms:
nethercote5da1e172003-12-03 21:44:45 +0000[diff] [blame]34
sewardjca456c72012-08-05 13:44:15 +0000[diff] [blame]35- X86/Linux
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]36- AMD64/Linux
37- PPC32/Linux
38- PPC64/Linux
sewardje089f012010-10-13 21:47:29 +0000[diff] [blame]39- ARM/Linux
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]40- x86/MacOSX
41- AMD64/MacOSX
floriandec4a562011-11-26 04:12:01 +0000[diff] [blame]42- S390X/Linux
sewardjca456c72012-08-05 13:44:15 +0000[diff] [blame]43- MIPS32/Linux
petarj4df0bfc2013-02-27 23:17:33 +0000[diff] [blame]44- MIPS64/Linux
Elliott Hughesa0664b92017-04-18 17:46:52 -0700[diff] [blame]45- X86/Solaris
46- AMD64/Solaris
njn567c0142006-03-31 12:24:37 +0000[diff] [blame]47
sewardjca456c72012-08-05 13:44:15 +0000[diff] [blame]48Note that AMD64 is just another name for x86_64, and Valgrind runs fine
njn4be4e2a2009-06-12 23:40:04 +0000[diff] [blame]49on Intel processors. Also note that the core of MacOSX is called
50"Darwin" and this name is used sometimes.
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]51
52Valgrind is licensed under the GNU General Public License, version 2.
njn25e49d8e72002-09-23 09:36:25 +0000[diff] [blame]53Read the file COPYING in the source distribution for details.
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]54
sewardje089f012010-10-13 21:47:29 +0000[diff] [blame]55However: if you contribute code, you need to make it available as GPL
56version 2 or later, and not 2-only.
57
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]58
59Documentation
60~~~~~~~~~~~~~
61A comprehensive user guide is supplied. Point your browser at
nethercote5da1e172003-12-03 21:44:45 +0000[diff] [blame]62$PREFIX/share/doc/valgrind/manual.html, where $PREFIX is whatever you
63specified with --prefix= when building.
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]64
65
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]66Building and installing it
67~~~~~~~~~~~~~~~~~~~~~~~~~~
njn0d733b82005-07-26 22:01:04 +0000[diff] [blame]68To install from the Subversion repository :
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]69
njn0d733b82005-07-26 22:01:04 +0000[diff] [blame]70 0. Check out the code from SVN, following the instructions at
njn1b70e822005-11-08 19:38:58 +0000[diff] [blame]71 http://www.valgrind.org/downloads/repository.html.
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]72
73 1. cd into the source directory.
74
75 2. Run ./autogen.sh to setup the environment (you need the standard
76 autoconf tools to do so).
77
njn0d733b82005-07-26 22:01:04 +0000[diff] [blame]78 3. Continue with the following instructions...
79
nethercote5da1e172003-12-03 21:44:45 +0000[diff] [blame]80To install from a tar.bz2 distribution:
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]81
njn801288e2009-08-04 07:02:54 +0000[diff] [blame]82 4. Run ./configure, with some options if you wish. The only interesting
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]83 one is the usual --prefix=/where/you/want/it/installed.
84
njn8b68b642009-06-24 00:37:09 +0000[diff] [blame]85 5. Run "make".
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]86
njn8b68b642009-06-24 00:37:09 +0000[diff] [blame]87 6. Run "make install", possibly as root if the destination permissions
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]88 require that.
89
njn0d733b82005-07-26 22:01:04 +0000[diff] [blame]90 7. See if it works. Try "valgrind ls -l". Either this works, or it
91 bombs out with some complaint. In that case, please let us know
92 (see www.valgrind.org).
nethercoteed7e0732003-12-02 15:30:28 +0000[diff] [blame]93
94Important! Do not move the valgrind installation into a place
95different from that specified by --prefix at build time. This will
96cause things to break in subtle ways, mostly when Valgrind handles
97fork/exec calls.
98
sewardjde4a1d02002-03-22 01:27:54 +0000[diff] [blame]99
njn1b70e822005-11-08 19:38:58 +0000[diff] [blame]100The Valgrind Developers