All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: linux-kernel@vger.kernel.org, Ulrich Drepper <drepper@redhat.com>
Subject: Re: libc/1427: gprof does not profile threads <synopsis of the problem
Date: Wed, 13 Mar 2002 20:25:21 -0800	[thread overview]
Message-ID: <3C902631.3A406D51@kegel.com> (raw)

Alan Cox wrote:
> Dan Kegel wrote:
> > I'm all in favor of a userspace fix.  I suggested a patch
> > to glibc to fix this.  Ulrich rejected it; I'm trying
> > to coax out of him how he thinks profiling of multithreaded
> > programs on Linux should be fixed.
> 
> Good and I'll reject any kernel patches 8)
> 
> If Ulrich won't talk then talk to the NGPT people. Maybe a little
> competition will warm things up.

Surely Ulrich will come up with a constructive proposal for
how to make gprof work with LinuxThreads.  He wouldn't
want an important tool like gprof to remain broken for
years, would he?

While I await his constructive response, perhaps I'll get my 
glibc patch in shape.
I am maintainer of what amounts to a tiny embedded linux
distribution, and I'm pretty sure my users would like
gprof to work.  (In fact, my boss's boss would really
like gprof to work.  This problem has a lot of visibility.)

- Dan

             reply	other threads:[~2002-03-14  4:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  4:25 Dan Kegel [this message]
2002-03-14 14:24 ` libc/1427: gprof does not profile threads <synopsis of the problem jlnance
2002-03-14 14:28 ` Alan Cox
2002-03-14 16:15   ` Dan Kegel
  -- 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=3C902631.3A406D51@kegel.com \
    --to=dank@kegel.com \
    --cc=drepper@redhat.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 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.