public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libc/1427: gprof does not profile threads <synopsis of the problem
Date: Thu, 14 Mar 2002 08:15:06 -0800	[thread overview]
Message-ID: <3C90CC8A.EF09EE83@kegel.com> (raw)
In-Reply-To: <E16lWD3-0000sj-00@the-village.bc.nu>

Dave McCracken <dmccr@us.ibm.com> wrote:
> > It even looks like kernel support is included 2.4.19-pre3:
> > 
> > http://oss.software.ibm.com/pthreads/
> > 
> > But don't see anything about it in any of the recent change logs...
> 
> The relevant line from the changelog is:
> 
> - Signal changes for thread groups                      (Dave McCracken)
> 
> This is the only patch that NGPT needs to work.

Does NGPT support profiling yet?  i.e. can I compile a program
using -pg and NGPT, and view the runtime distribution histogram
with gprof?

- Dan

  reply	other threads:[~2002-03-14 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  4:25 libc/1427: gprof does not profile threads <synopsis of the problem Dan Kegel
2002-03-14 14:24 ` jlnance
2002-03-14 14:28 ` Alan Cox
2002-03-14 16:15   ` Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-14  0:19 libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)> Dan Kegel
2002-03-14  1:28 ` libc/1427: gprof does not profile threads <synopsis of the problem Alan Cox
2002-03-14  1:08   ` Dan Kegel
2002-03-14  3:00     ` Alan Cox
2002-03-14  2:55       ` Jeff Garzik
2002-03-14  3:26         ` David Rees
2002-03-14 15:51           ` Dave McCracken
2002-03-14 15:58     ` Daniel Phillips

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=3C90CC8A.EF09EE83@kegel.com \
    --to=dank@kegel.com \
    --cc=dmccr@us.ibm.com \
    --cc=linux-kernel@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