From: Holger Freyther <holger+oe@freyther.de>
To: Steffen Sledz <sledz@dresearch.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: profiling howto?
Date: Thu, 03 Feb 2011 14:10:52 +0100 [thread overview]
Message-ID: <4D4AA95C.5000103@freyther.de> (raw)
In-Reply-To: <4D4AA84C.1050001@dresearch.de>
On 02/03/2011 02:06 PM, Steffen Sledz wrote:
>> I am not sure why you want to use gprof but anyway...
>>
>> a) do not use gprof on glibc...
>
> I'm not interested in using gprof on glibc. I'm interested in profiling some other libs/apps only.
>
> But the suggested method to prepare just some packages for profiling does not work jet (see other subthread).
1.) use oprofile... install the -dbg packages on the device... install
oprofile itself... start sampling with opcontrol --start -p library -c 7 or
such.. then stop... use opreport -l to look...
2.) if you want to have backtraces... recompile with -fno-omit-frame-pointer
as I have mentioned...
3.) if you do not want sampling based profiling, yes use gprof... enable it
for the libs and apps you want... using bitbake -e you should be able to
figure out how bitbake selects the variables...
next prev parent reply other threads:[~2011-02-03 13:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 9:54 profiling howto? Steffen Sledz
2011-02-02 10:11 ` Holger Freyther
2011-02-02 11:12 ` Henning Heinold
2011-02-02 12:59 ` Steffen Sledz
2011-02-02 13:12 ` Holger Freyther
2011-02-03 8:05 ` Steffen Sledz
2011-02-03 9:00 ` Holger Freyther
2011-02-03 10:44 ` Steffen Sledz
2011-02-03 8:30 ` Steffen Sledz
2011-02-03 8:54 ` Jan Paesmans
2011-02-03 10:52 ` Steffen Sledz
2011-02-03 11:30 ` Holger Freyther
2011-02-03 11:50 ` Steffen Sledz
2011-02-03 11:53 ` Holger Freyther
2011-02-03 12:07 ` Steffen Sledz
2011-02-03 12:14 ` Holger Freyther
2011-02-03 13:06 ` Steffen Sledz
2011-02-03 13:10 ` Holger Freyther [this message]
2011-02-04 12:09 ` Steffen Sledz
2011-02-03 14:25 ` Phil Blundell
[not found] ` <1296735116.2258.44.camel@phil-desktop>
2011-02-03 14:25 ` Phil Blundell
2011-02-03 22:34 ` Khem Raj
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=4D4AA95C.5000103@freyther.de \
--to=holger+oe@freyther.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sledz@dresearch.de \
/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