third_party/tcmalloc/vendor/doc/cpuprofile.html - Issue 9316021: Update the tcmalloc vendor branch to r144 (gperftools 2.0).

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: third_party/tcmalloc/vendor/doc/cpuprofile.html

Issue 9316021: Update the tcmalloc vendor branch to r144 (gperftools 2.0). (Closed) Base URL: http://git.chromium.org/git/chromium.git@trunk

Patch Set: Reuploading Created 8 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: third_party/tcmalloc/vendor/doc/cpuprofile.html

diff --git a/third_party/tcmalloc/vendor/doc/cpuprofile.html b/third_party/tcmalloc/vendor/doc/cpuprofile.html

index f029e787ac07d87585b82e6b1a5989d1f39f84ad..769ec68f3d3b34c45b399fb80f933917095437dd 100644

--- a/third_party/tcmalloc/vendor/doc/cpuprofile.html

+++ b/third_party/tcmalloc/vendor/doc/cpuprofile.html

@@ -3,7 +3,7 @@

<HEAD>

- <title>Google CPU Profiler</title>

+ <title>Gperftools CPU Profiler</title>

</HEAD>

<BODY>

@@ -50,13 +50,14 @@ for a given run of an executable:

<ol>

<li> 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>:

- <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:

+ <pre>% env CPUPROFILE=ls.prof /bin/ls</pre>

<li> 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.

</ol>

@@ -71,7 +72,7 @@ CPUPROFILE with the child's process id).

For security reasons, CPU profiling will not write to a file -- and

is thus not usable -- for setuid programs.

-See the include-file <code>google/profiler.h</code> for

+See the include-file <code>gperftools/profiler.h</code> for

advanced-use functions, including <code>ProfilerFlush()</code> and

<code>ProfilerStartWithOptions()</code>.

« no previous file with comments | « third_party/tcmalloc/vendor/depcomp ('k') | third_party/tcmalloc/vendor/doc/designstyle.css » ('j') | no next file with comments »