blob: fc6996ea12f2762277d9060a296f13fe0fddd67c [file] [log] [blame]
<html>
<head>
<style type="text/css">
body { background-color: #ffffff;
color: #000000;
font-family: Times, Helvetica, Arial;
font-size: 14pt}
h4 { margin-bottom: 0.3em}
code { color: #000000;
font-family: Courier;
font-size: 13pt }
pre { color: #000000;
font-family: Courier;
font-size: 13pt }
a:link { color: #0000C0;
text-decoration: none; }
a:visited { color: #0000C0;
text-decoration: none; }
a:active { color: #0000C0;
text-decoration: none; }
</style>
<title>Cachegrind</title>
</head>
<body bgcolor="#ffffff">
<a name="title"></a>
<h1 align=center>Nulgrind</h1>
<center>This manual was last updated on 2002-10-02</center>
<p>
<center>
<a href="mailto:njn25@cam.ac.uk">njn25@cam.ac.uk</a><br>
Copyright &copy; 2000-2003 Nicholas Nethercote
<p>
Nulgrind is licensed under the GNU General Public License,
version 2<br>
Nulgrind is a Valgrind tool that does not very much at all.
</center>
<p>
<h2>1&nbsp; Nulgrind</h2>
Nulgrind is the minimal tool for Valgrind. It does no initialisation or
finalisation, and adds no instrumentation to the program's code. It is mainly
of use for Valgrind's developers for debugging and regression testing.
<p>
Nonetheless you can run programs with Nulgrind. They will run roughly 5-10
times more slowly than normal, for no useful effect. Note that you need to use
the option <code>--tool=none</code> to run Nulgrind (ie. not
<code>--tool=nulgrind</code>).
<hr width="100%">
</body>
</html>