diff options
| author | dmikurube@chromium.org <dmikurube@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-14 20:07:36 +0000 |
|---|---|---|
| committer | dmikurube@chromium.org <dmikurube@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-14 20:07:36 +0000 |
| commit | 3b7b385aaffaafb4b07f71d037d923dcf1ed9f3b (patch) | |
| tree | 3acf3170028811c172ebc7e119184632ef0181a5 /third_party/tcmalloc/vendor/doc/cpuprofile.html | |
| parent | 2cc7f51461d757d19abc2f8dd7dbd17d82d9788d (diff) | |
| download | chromium_src-3b7b385aaffaafb4b07f71d037d923dcf1ed9f3b.zip chromium_src-3b7b385aaffaafb4b07f71d037d923dcf1ed9f3b.tar.gz chromium_src-3b7b385aaffaafb4b07f71d037d923dcf1ed9f3b.tar.bz2 | |
Update the tcmalloc vendor branch to r144 (gperftools 2.0).
The major reason for us to enable a fix for HEAP_PROFILE_MMAP.
Please note that this change doesn't affect Chromium builds.
BUG=114302
TEST=none
Review URL: https://chromiumcodereview.appspot.com/9316021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126715 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/tcmalloc/vendor/doc/cpuprofile.html')
| -rw-r--r-- | third_party/tcmalloc/vendor/doc/cpuprofile.html | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/third_party/tcmalloc/vendor/doc/cpuprofile.html b/third_party/tcmalloc/vendor/doc/cpuprofile.html index f029e78..769ec68 100644 --- a/third_party/tcmalloc/vendor/doc/cpuprofile.html +++ b/third_party/tcmalloc/vendor/doc/cpuprofile.html @@ -3,7 +3,7 @@ <HEAD> <link rel="stylesheet" href="designstyle.css"> - <title>Google CPU Profiler</title> + <title>Gperftools CPU Profiler</title> </HEAD> <BODY> @@ -50,13 +50,14 @@ for a given run of an executable:</p> <ol> <li> <p>Define the environment variable CPUPROFILE to the filename - 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> + 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> <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><google/profiler.h></code>.) + (These functions are declared in <code><gperftools/profiler.h></code>.) <code>ProfilerStart()</code> will take the profile-filename as an argument.</p> </ol> @@ -71,7 +72,7 @@ CPUPROFILE with the child's process id).</p> <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>google/profiler.h</code> for +<p>See the include-file <code>gperftools/profiler.h</code> for advanced-use functions, including <code>ProfilerFlush()</code> and <code>ProfilerStartWithOptions()</code>.</p> |