All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@baldric.uwo.ca>
To: linux-ia64@vger.kernel.org
Subject: Re: [carlos@baldric.uwo.ca: Good news for glibc.]
Date: Mon, 05 Jan 2004 19:31:54 +0000	[thread overview]
Message-ID: <20040105193154.GA9157@systemhalted> (raw)
In-Reply-To: <20040105183349.GC9004@colo.lackof.org>

On Mon, Jan 05, 2004 at 11:06:38AM -0800, David Mosberger wrote:
> 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... ;-)

Indeed! Looks very cool though.

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

Looks good, It was just my wish to get LD_PROFILE working, what's easier
than tacking on an environment variable to get a quick look at the calls
made by a particular DSO?

I'm 99.9% sure if upstream takes my patches this will fix LD_PROFILE
for ia64 aswell.

c.


  parent reply	other threads:[~2004-01-05 19:31 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
2004-01-05 19:31 ` Carlos O'Donell [this message]
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=20040105193154.GA9157@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.