svn commit: r228143 - in head: . share/mk tools/build/options
Steve Kargl
sgk at troutmask.apl.washington.edu
Mon Dec 19 20:41:34 UTC 2011
On Mon, Dec 19, 2011 at 08:09:32PM +0000, David Chisnall wrote:
> On 19 Dec 2011, at 19:52, Warner Losh wrote:
>
> > -1. The needs of the many? Please. Let's break a useful feature because some people don't understand it and are impatient? That's lame.
>
> How useful is gprof-based profiling these days? Now that we
> have the DTrace pid provider, don't we have access to much more
> fine-grained profiling information without the need for shipping
> two versions of every library?
It is quite uesful given that for the last 20 or so years,
I can do
cc -o z -pg a.c -lm_p
./z
gprof -b -l ./z z.gmon | more
% cumulative self self total
time seconds seconds calls ms/call ms/call name
72.1 0.91 0.91 0 100.00% _mcount [1]
11.1 1.05 0.14 8388608 0.00 0.00 sinf [4]
8.2 1.16 0.10 8388608 0.00 0.00 nextafterf [5]
4.6 1.21 0.06 0 100.00% .mcount (9)
to ge the information I want.
dtrace(1M) does not seem to contain an example that gives the
equivalent information. In fact, the manpage contains no examples,
only the statement:
See the Solaris Dynamic Tracing Guide for detailed examples
of how to use the dtrace utility to perform these tasks.
which, of course, is not very useful given that I do not have a
Solaris Dynamic Tracing Guide.
--
Steve
More information about the svn-src-head
mailing list