From: Jakub Jelinek <jakub@redhat.com>
To: Dan Kegel <dkegel@ixiacom.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
darkeye@tyrell.hu, libc-gnats@gnu.org, gnats-admin@cygnus.com,
sam@zoy.org, Xavier Leroy <Xavier.Leroy@inria.fr>,
linux-kernel@vger.kernel.org, babt@us.ibm.com
Subject: Re: libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)>
Date: Thu, 14 Mar 2002 02:08:34 -0500 [thread overview]
Message-ID: <20020314020834.Z2434@devserv.devel.redhat.com> (raw)
In-Reply-To: <1016062486.16743.1091.camel@myware.mynet> <3C8FEC76.F1411739@ixiacom.com>
In-Reply-To: <3C8FEC76.F1411739@ixiacom.com>; from dkegel@ixiacom.com on Wed, Mar 13, 2002 at 04:19:02PM -0800
On Wed, Mar 13, 2002 at 04:19:02PM -0800, Dan Kegel wrote:
> Ulrich Drepper wrote:
> >
> > On Wed, 2002-03-13 at 15:17, Dan Kegel wrote:
> >
> > > So let's break the logjam and fix glibc's linuxthreads' pthread_create
> > > to [support profiling multithreaded programs]
> >
> > I will add nothing like this. The implementation is broken enough and
> > any addition just makes it worse. If you patch your own code you'll get
> > what you want at your own risk.
>
> OK. What's the right way to fix this, then?
Surely don't use timer for profiling.
Have the compiler generate profiling calls both at function entry and exit
and use rdtsc/whatever other register your machine has (or even better
profiling registers) to note time of that function being entered/left.
Jakub
next prev parent reply other threads:[~2002-03-14 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 23:17 libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)> Dan Kegel
2002-03-13 23:34 ` Ulrich Drepper
2002-03-14 0:19 ` 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
2002-03-14 7:08 ` Jakub Jelinek [this message]
2002-03-14 13:19 ` libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)> John Levon
2002-03-15 21:56 ` Dan Kegel
2002-03-16 0:19 ` Ulrich Drepper
2002-03-16 1:41 ` libc/1427: gprof does not profile threads <synopsis of the Alan Cox
2002-03-16 2:40 ` libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)> Erik Andersen
2002-03-16 13:12 ` Olaf Dietsche
2002-03-16 16:57 ` Daniel Egger
2002-03-14 16:07 ` Daniel Phillips
2002-03-14 16:25 ` Richard Gooch
2002-03-14 16:47 ` 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=20020314020834.Z2434@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Xavier.Leroy@inria.fr \
--cc=babt@us.ibm.com \
--cc=darkeye@tyrell.hu \
--cc=dkegel@ixiacom.com \
--cc=drepper@redhat.com \
--cc=gnats-admin@cygnus.com \
--cc=libc-gnats@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@zoy.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.