mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
wibbles
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1104
This commit is contained in:
parent
ee70f4950b
commit
f68cbf9ea9
@ -19,13 +19,13 @@
|
||||
a:active { color: #0000C0;
|
||||
text-decoration: none; }
|
||||
</style>
|
||||
<title>Valgrind</title>
|
||||
<title>Cachegrind</title>
|
||||
</head>
|
||||
|
||||
<body bgcolor="#ffffff">
|
||||
|
||||
<a name="title"> </a>
|
||||
<h1 align=center>Valgrind, version 1.0.0</h1>
|
||||
<h1 align=center>Cachegrind, version 1.0.0</h1>
|
||||
<center>This manual was last updated on 20020726</center>
|
||||
<p>
|
||||
|
||||
@ -73,10 +73,10 @@ Any feedback, bug-fixes, suggestions, etc, welcome.
|
||||
|
||||
|
||||
<h3>1.1 Overview</h3>
|
||||
First off, as for normal Valgrind use, you probably want to turn on debugging
|
||||
info (the <code>-g</code> flag). But by contrast with normal Valgrind use, you
|
||||
probably <b>do</b> want to turn optimisation on, since you should profile your
|
||||
program as it will be normally run.
|
||||
First off, as for normal Valgrind use, you probably want to compile with
|
||||
debugging info (the <code>-g</code> flag). But by contrast with normal
|
||||
Valgrind use, you probably <b>do</b> want to turn optimisation on, since you
|
||||
should profile your program as it will be normally run.
|
||||
|
||||
The two steps are:
|
||||
<ol>
|
||||
|
||||
@ -26,7 +26,7 @@
|
||||
|
||||
<body>
|
||||
<h2>Documentation Contents</h2>
|
||||
<a href="../core/docs/index.html"><b>Core</b></a><br>
|
||||
<a href="../coregrind/docs/index.html"><b>Core</b></a><br>
|
||||
<a href="../memcheck/docs/index.html"><b>memcheck</b></a><br>
|
||||
<a href="../cachegrind/docs/index.html"><b>Cachegrind</b></a><br>
|
||||
</body>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user