Date: Tue, 19 Jun 2007 05:16:09 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Garrett Cooper <youshi10@u.washington.edu> Cc: hackers@freebsd.org Subject: Re: Making sense of ktrace(1) output Message-ID: <20070618191609.GM1181@turion.vk2pj.dyndns.org> In-Reply-To: <20070618133711.GA94692@freebsd.org> References: <467636C0.6040604@u.washington.edu> <20070618081532.GI1181@turion.vk2pj.dyndns.org> <46764865.9030203@u.washington.edu> <20070618133711.GA94692@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 2007-Jun-18 15:37:11 +0200, Roman Divacky <rdivacky@freebsd.org> wrote: >well.. instead of using ktrace I'd suggest building profiled pkg_add >and see that way where the time is spent. ktrace is great if you dont >have the source code... but you do :) If you decide to go this route, you might like to apply http://www.freebsd.org/cgi/query-pr.cgi?pr=99800 By default gmon.out is overwritten by each process so you will only get the output from the last process of a given name. My patch optionally saves the profiling output each process in a separate file. gprof(1) can already accumulate the output from multiple files so this patch gives you the ability to profile multiple executions of a single executable. You will still need to glue together the profiling results from each executable. -- Peter Jeremy [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGdtn5/opHv/APuIcRAmkyAKCboAL6jB2sRTjQluQcvc+tPlpSOACfbzet gJzXr6ckSL6Mk/PdT9nopf4= =AIBr -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070618191609.GM1181>