From c8ba0a40b46bd56fdad011c841ba1d98be05384e Mon Sep 17 00:00:00 2001 From: Dmitriy Vyukov Date: Sat, 22 Sep 2012 05:54:36 +1000 Subject: [PATCH] [release-branch.go1] runtime/pprof: fix comments MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit ««« backport e7e49c318134 runtime/pprof: fix comments R=golang-dev, iant CC=golang-dev https://golang.org/cl/6460082 »»» --- src/pkg/runtime/pprof/pprof.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pkg/runtime/pprof/pprof.go b/src/pkg/runtime/pprof/pprof.go index f67e8a8f9a..48e8b92f97 100644 --- a/src/pkg/runtime/pprof/pprof.go +++ b/src/pkg/runtime/pprof/pprof.go @@ -23,7 +23,7 @@ import ( // BUG(rsc): A bug in the OS X Snow Leopard 64-bit kernel prevents // CPU profiling from giving accurate results on that system. -// A Profile is a collection of stack traces showing the call sequences +// Profile is a collection of stack traces showing the call sequences // that led to instances of a particular event, such as allocation. // Packages can create and maintain their own profiles; the most common // use is for tracking resources that must be explicitly closed, such as files @@ -250,7 +250,7 @@ func (x stackProfile) Less(i, j int) bool { return len(t) < len(u) } -// A countProfile is a set of stack traces to be printed as counts +// countProfile is a set of stack traces to be printed as counts // grouped by stack trace. There are multiple implementations: // all that matters is that we can find out how many traces there are // and obtain each trace in turn. @@ -356,7 +356,7 @@ func countHeap() int { return n } -// writeHeapProfile writes the current runtime heap profile to w. +// writeHeap writes the current runtime heap profile to w. func writeHeap(w io.Writer, debug int) error { // Find out how many records there are (MemProfile(nil, false)), // allocate that many records, and get the data. -- 2.50.0