njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 1 | <?xml version="1.0"?> <!-- -*- sgml -*- --> |
| 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" |
| 4 | [ <!ENTITY % vg-entities SYSTEM "vg-entities.xml"> %vg-entities; ]> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 5 | |
| 6 | <chapter id="manual-intro" xreflabel="Introduction"> |
| 7 | <title>Introduction</title> |
| 8 | |
| 9 | <sect1 id="manual-intro.overview" xreflabel="An Overview of Valgrind"> |
| 10 | <title>An Overview of Valgrind</title> |
| 11 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 12 | <para>Valgrind is an instrumentation framework for building dynamic analysis |
| 13 | tools. It comes with a set of tools each of which performs some kind of |
| 14 | debugging, profiling, or similar task that helps you improve your programs. |
| 15 | Valgrind's architecture is modular, so new tools can be created easily |
| 16 | and without disturbing the existing structure.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 17 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 18 | <para>A number of useful tools are supplied as standard.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 19 | |
| 20 | <orderedlist> |
| 21 | |
| 22 | <listitem> |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 23 | <para><command>Memcheck</command> is a memory error detector. It helps |
| 24 | you make your programs, particularly those written in C and C++, more |
| 25 | correct.</para> |
| 26 | </listitem> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 27 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 28 | <listitem> |
| 29 | <para><command>Cachegrind</command> is a cache and branch-prediction |
njn | 7316df2 | 2009-08-04 01:16:01 +0000 | [diff] [blame] | 30 | profiler. It helps you make your programs run faster.</para> |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 31 | </listitem> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 32 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 33 | <listitem> |
| 34 | <para><command>Callgrind</command> is a call-graph generating cache |
| 35 | profiler. It has some overlap with Cachegrind, but also gathers some |
| 36 | information that Cachegrind does not.</para> |
| 37 | </listitem> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 38 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 39 | <listitem> |
| 40 | <para><command>Helgrind</command> is a thread error detector. |
njn | 7316df2 | 2009-08-04 01:16:01 +0000 | [diff] [blame] | 41 | It helps you make your multi-threaded programs more correct. |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 42 | </para> |
| 43 | </listitem> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 44 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 45 | <listitem> |
| 46 | <para><command>DRD</command> is also a thread error detector. It is |
| 47 | similar to Helgrind but uses different analysis techniques and so may |
| 48 | find different problems.</para> |
| 49 | </listitem> |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 50 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 51 | <listitem> |
njn | 7316df2 | 2009-08-04 01:16:01 +0000 | [diff] [blame] | 52 | <para><command>Massif</command> is a heap profiler. It helps you |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 53 | make your programs use less memory.</para> |
| 54 | </listitem> |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 55 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 56 | <listitem> |
sewardj | e089f01 | 2010-10-13 21:47:29 +0000 | [diff] [blame] | 57 | <para><command>DHAT</command> is a different kind of heap |
| 58 | profiler. It helps you understand issues of block lifetimes, |
| 59 | block utilisation, and layout inefficiencies.</para> |
| 60 | </listitem> |
| 61 | |
| 62 | <listitem> |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 63 | <para><command>Ptrcheck</command> is an experimental heap, stack and |
| 64 | global array overrun detector. Its functionality overlaps somewhat |
| 65 | with Memcheck's, but it can find some problems that Memcheck would |
| 66 | miss.</para> |
| 67 | </listitem> |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 68 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 69 | <listitem> |
| 70 | <para><command>BBV</command> is an experimental SimPoint basic block |
| 71 | vector generator. It is useful to people doing computer architecture |
| 72 | research and development.</para> |
| 73 | </listitem> |
njn | 218714b | 2009-06-02 23:20:40 +0000 | [diff] [blame] | 74 | |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 75 | </orderedlist> |
| 76 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 77 | <para>There are also a couple of minor tools that aren't useful to |
| 78 | most users: <command>Lackey</command> is an example tool that illustrates |
| 79 | some instrumentation basics; and <command>Nulgrind</command> is the minimal |
| 80 | Valgrind tool that does no analysis or instrumentation, and is only useful |
| 81 | for testing purposes.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 82 | |
njn | 779a2d6 | 2005-07-25 00:12:19 +0000 | [diff] [blame] | 83 | <para>Valgrind is closely tied to details of the CPU and operating |
| 84 | system, and to a lesser extent, the compiler and basic C libraries. |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 85 | Nonetheless, it supports a number of widely-used platforms, listed in full |
| 86 | at <ulink url="&vg-url;">&vg-url;</ulink>.</para> |
| 87 | |
| 88 | <para>Valgrind is built via the standard Unix |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 89 | <computeroutput>./configure</computeroutput>, |
| 90 | <computeroutput>make</computeroutput>, <computeroutput>make |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 91 | install</computeroutput> process; full details are given in the |
| 92 | README file in the distribution.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 93 | |
| 94 | <para>Valgrind is licensed under the <xref linkend="license.gpl"/>, |
de | bad57fc | 2005-12-03 22:33:29 +0000 | [diff] [blame] | 95 | version 2. The <computeroutput>valgrind/*.h</computeroutput> headers |
| 96 | that you may wish to include in your code (eg. |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 97 | <filename>valgrind.h</filename>, <filename>memcheck.h</filename>, |
njn | 218714b | 2009-06-02 23:20:40 +0000 | [diff] [blame] | 98 | <filename>helgrind.h</filename>, etc.) are |
de | bad57fc | 2005-12-03 22:33:29 +0000 | [diff] [blame] | 99 | distributed under a BSD-style license, so you may include them in your |
| 100 | code without worrying about license conflicts. Some of the PThreads |
| 101 | test cases, <filename>pth_*.c</filename>, are taken from "Pthreads |
| 102 | Programming" by Bradford Nichols, Dick Buttlar & Jacqueline Proulx |
| 103 | Farrell, ISBN 1-56592-115-1, published by O'Reilly & Associates, |
| 104 | Inc.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 105 | |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 106 | <para>If you contribute code to Valgrind, please ensure your |
| 107 | contributions are licensed as "GPLv2, or (at your option) any later |
| 108 | version." This is so as to allow the possibility of easily upgrading |
| 109 | the license to GPLv3 in future. If you want to modify code in the VEX |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 110 | subdirectory, please also see the file VEX/HACKING.README in the |
| 111 | distribution.</para> |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 112 | |
| 113 | |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 114 | </sect1> |
| 115 | |
| 116 | |
| 117 | <sect1 id="manual-intro.navigation" xreflabel="How to navigate this manual"> |
| 118 | <title>How to navigate this manual</title> |
| 119 | |
njn | 05a8917 | 2009-07-29 02:36:21 +0000 | [diff] [blame] | 120 | <para>This manual's structure reflects the structure of Valgrind itself. |
njn | f4b4758 | 2009-08-10 01:15:30 +0000 | [diff] [blame] | 121 | First, we describe the Valgrind core, how to use it, and the options |
de | bad57fc | 2005-12-03 22:33:29 +0000 | [diff] [blame] | 122 | it supports. Then, each tool has its own chapter in this manual. You |
| 123 | only need to read the documentation for the core and for the tool(s) you |
| 124 | actually use, although you may find it helpful to be at least a little |
sewardj | 3387889 | 2007-11-17 09:43:25 +0000 | [diff] [blame] | 125 | bit familiar with what all tools do. If you're new to all this, you probably |
njn | 7316df2 | 2009-08-04 01:16:01 +0000 | [diff] [blame] | 126 | want to run the Memcheck tool and you might find the <xref |
| 127 | linkend="quick-start"/> useful.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 128 | |
njn | f4b4758 | 2009-08-10 01:15:30 +0000 | [diff] [blame] | 129 | <para>Be aware that the core understands some command line options, and |
| 130 | the tools have their own options which they know about. This means |
| 131 | there is no central place describing all the options that are |
| 132 | accepted -- you have to read the options documentation both for |
de | bad57fc | 2005-12-03 22:33:29 +0000 | [diff] [blame] | 133 | <xref linkend="manual-core"/> and for the tool you want to use.</para> |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 134 | |
sewardj | 778d783 | 2007-11-22 01:21:56 +0000 | [diff] [blame] | 135 | |
njn | 3e986b2 | 2004-11-30 10:43:45 +0000 | [diff] [blame] | 136 | </sect1> |
| 137 | |
| 138 | </chapter> |