public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [carlos@baldric.uwo.ca: Good news for glibc.]
Date: Mon, 05 Jan 2004 19:06:38 +0000	[thread overview]
Message-ID: <16377.46526.239285.352586@napali.hpl.hp.com> (raw)
In-Reply-To: <20040105183349.GC9004@colo.lackof.org>

>>>>> On Mon, 5 Jan 2004 11:33:49 -0700, Grant Grundler <grundler@parisc-linux.org> said:

  Grant> glibc profiling?  This was originally posted on
  Grant> debian-hppa/parisc-linux mailing lists.

I'd recommend q-tools.  It will give you a (statistically collected)
call-graph, in addition to the flat profile and is completely
unintrusive (no recompilation etc needed).  See my post for details:

  http://marc.theaimsgroup.com/?l=linux-ia64&m\x107075994721581

Oh, yeah, I'm slightly biased... ;-)

The one limitation is that it doesn't work well for short-lived
processes.  Also, it works in system-wide mode (collects info for
_all_ processes that happen to run over a given period of time).

If you want per-process profiling, you could use qprof.  It doesn't do
call-graphs (yet) and only works for dynamically linked programs, but
it's very easy to use.  See:

  http://www.hpl.hp.com/research/linux/qprof/

	--david

  reply	other threads:[~2004-01-05 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 18:33 [carlos@baldric.uwo.ca: Good news for glibc.] Grant Grundler
2004-01-05 19:06 ` David Mosberger [this message]
2004-01-05 19:31 ` Carlos O'Donell
2004-01-05 22:07 ` David Mosberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16377.46526.239285.352586@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox