| Index: third_party/tcmalloc/vendor/doc/cpuprofile.html
|
| ===================================================================
|
| --- third_party/tcmalloc/vendor/doc/cpuprofile.html (revision 126727)
|
| +++ third_party/tcmalloc/vendor/doc/cpuprofile.html (working copy)
|
| @@ -3,7 +3,7 @@
|
|
|
| <HEAD>
|
| <link rel="stylesheet" href="designstyle.css">
|
| - <title>Gperftools CPU Profiler</title>
|
| + <title>Google CPU Profiler</title>
|
| </HEAD>
|
|
|
| <BODY>
|
| @@ -50,14 +50,13 @@
|
|
|
| <ol>
|
| <li> <p>Define the environment variable CPUPROFILE to the filename
|
| - to dump the profile to. For instance, if you had a version of
|
| - <code>/bin/ls</code> that had been linked against libprofiler,
|
| - you could run:</p>
|
| - <pre>% env CPUPROFILE=ls.prof /bin/ls</pre>
|
| + to dump the profile to. For instance, to profile
|
| + <code>/usr/local/bin/my_binary_compiled_with_libprofiler_so</code>:</p>
|
| + <pre>% env CPUPROFILE=/tmp/mybin.prof /usr/local/bin/my_binary_compiled_with_libprofiler_so</pre>
|
|
|
| <li> <p>In your code, bracket the code you want profiled in calls to
|
| <code>ProfilerStart()</code> and <code>ProfilerStop()</code>.
|
| - (These functions are declared in <code><gperftools/profiler.h></code>.)
|
| + (These functions are declared in <code><google/profiler.h></code>.)
|
| <code>ProfilerStart()</code> will take
|
| the profile-filename as an argument.</p>
|
| </ol>
|
| @@ -72,7 +71,7 @@
|
| <p>For security reasons, CPU profiling will not write to a file -- and
|
| is thus not usable -- for setuid programs.</p>
|
|
|
| -<p>See the include-file <code>gperftools/profiler.h</code> for
|
| +<p>See the include-file <code>google/profiler.h</code> for
|
| advanced-use functions, including <code>ProfilerFlush()</code> and
|
| <code>ProfilerStartWithOptions()</code>.</p>
|
|
|
|
|