From: Daniel Egger <degger@fhm.edu>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)>
Date: 16 Mar 2002 17:57:59 +0100 [thread overview]
Message-ID: <1016297880.18342.32.camel@sonja> (raw)
In-Reply-To: <1016237961.5612.51.camel@myware.mynet>
In-Reply-To: <1016062486.16743.1091.camel@myware.mynet> <3C8FEC76.F1411739@ixiacom.com> <20020314020834.Z2434@devserv.devel.redhat.com> <3C926E0B.1A0EE311@ixiacom.com> <1016237961.5612.51.camel@myware.mynet>
Am Sam, 2002-03-16 um 01.19 schrieb Ulrich Drepper:
> > Ulrich, do you at least agree that it would be desirable for
> > gprof to work properly on multithreaded programs?
> No. gprof is uselss in today world.
Interesting. Care to share your reason for this assumption?
--
Servus,
Daniel
next prev parent reply other threads:[~2002-03-16 18:21 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 ` libc/1427: gprof does not profile threads <synopsis of the problem (one li\ne)> Jakub Jelinek
2002-03-14 13:19 ` 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 [this message]
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=1016297880.18342.32.camel@sonja \
--to=degger@fhm.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox