From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: gprof, threads and forks
Date: Wed, 5 Sep 2001 20:11:42 -0700 [thread overview]
Message-ID: <20010905201142.D1618@mikef-linux.matchmail.com> (raw)
In-Reply-To: <HBEHIIBBKKNOBLMPKCBBEEKODKAA.znmeb@aracnet.com>
In-Reply-To: <HBEHIIBBKKNOBLMPKCBBEEKODKAA.znmeb@aracnet.com>
On Wed, Sep 05, 2001 at 08:04:00PM -0700, M. Edward Borasky wrote:
> fixed?" I need to profile a multi-threaded executable and personally don't
> care about the "fork" case, but I'm sure there are others who would care
> about forks and not threads.
Did you try testing against an -ac kernel? I believe there is a patch in
there that allows profiling of multi-threaded apps. If it has made it into
the main kernel, then you can just ignore this message...
next prev parent reply other threads:[~2001-09-06 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 3:04 gprof, threads and forks M. Edward Borasky
2001-09-06 3:11 ` Mike Fedyk [this message]
2001-09-06 3:42 ` Ian Lance Taylor
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=20010905201142.D1618@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.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