From: Nicholas Nethercote Date: Mon, 23 Sep 2002 16:56:39 +0000 (+0000) Subject: wibbles X-Git-Tag: svn/VALGRIND_1_9_4~313 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f68cbf9ea944c23bc3b3dccf215b09b26ac66f43;p=thirdparty%2Fvalgrind.git wibbles git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1104 --- diff --git a/cachegrind/docs/manual.html b/cachegrind/docs/manual.html index 9af1ec200a..2379a19666 100644 --- a/cachegrind/docs/manual.html +++ b/cachegrind/docs/manual.html @@ -19,13 +19,13 @@ a:active { color: #0000C0; text-decoration: none; } - Valgrind + Cachegrind -

Valgrind, version 1.0.0

Cachegrind, version 1.0.0

This manual was last updated on 20020726

@@ -73,10 +73,10 @@ Any feedback, bug-fixes, suggestions, etc, welcome.

1.1 Overview

-First off, as for normal Valgrind use, you probably want to turn on debugging -info (the -g flag). But by contrast with normal Valgrind use, you -probably do 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 -g flag). But by contrast with normal +Valgrind use, you probably do want to turn optimisation on, since you +should profile your program as it will be normally run. The two steps are:

Documentation Contents

Core

memcheck

Cachegrind