From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: binutils@sources.redhat.com
Subject: Re: gprof
Date: Tue, 20 Sep 2005 14:13:00 -0000 [thread overview]
Message-ID: <43300F48.2020602@gandalf.sssup.it> (raw)
In-Reply-To: <A9BD19EF-6D57-4E6F-AD3A-A932C8FFCEC9@raeburn.org>
Ken Raeburn wrote:
> On Sep 15, 2005, at 04:45, Michael Trimarchi wrote:
>
>> Hi all,
>> I'd like to profile multithread application using gprof, but I
>> cannot profile thread !!! why?
>> Is the ITIMER signal problem?
>> regards
>> Michael
>
>
> I've tried this before... yes, depending on the system, you may need
> to play some games after thread creation to start profiling in the
> newly created thread, such as explicitly scheduling an interrupt
> timer. But also, if you care about the accuracy of the results, you
> may need to modify the C runtime support code for profiling, which
> typically updates the per-function data in a manner that is not
> thread-safe.
>
> Unfortunately, I don't have any code to show you for either issue,
> right now...
>
> Ken
>But also, if you care about the accuracy of the results, you may need
to modify the C runtime support code for >profiling, which typically
updates the per-function data in a manner that is not thread-safe.
may you explain more precisely this point?
Regards
Michael
next prev parent reply other threads:[~2005-09-20 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 10:54 gprof Michael Trimarchi
2005-09-15 12:31 ` gprof Ken Raeburn
2005-09-20 14:13 ` Michael Trimarchi [this message]
2005-09-20 18:12 ` gprof Ken Raeburn
2005-09-27 10:59 ` gprof Michael Trimarchi
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=43300F48.2020602@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=binutils@sources.redhat.com \
--cc=raeburn@raeburn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).