From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Profiling binaries?
Date: Mon, 22 Oct 2012 14:30:43 +0100 [thread overview]
Message-ID: <50854A83.2050106@communistcode.co.uk> (raw)
In-Reply-To: <CAGiJk9eWrfnX68DDVLFcqzmG4fo4xEz=wpyKgjwtcP2__=x+EQ@mail.gmail.com>
On 22/10/12 14:23, Samuel Stirtzel wrote:
> 2012/10/22 Steffen Sledz <sledz@dresearch-fe.de>:
>> On 22.10.2012 15:12, Samuel Stirtzel wrote:
>>> 2012/10/22 Steffen Sledz <sledz@dresearch-fe.de>:
>>>> Just a short question: Does oe[-core] provide a generic method to create packages containing binaries/libraries with profiling support?
>>>>
>>> Depending on your platform you could use Valgrind [1], or to be more
>>> specific Callgrind [2].
>>>
>>> The recipe is in .../openembedded-core/meta/recipes-devtools/valgrind/
>>> you can check there if your arch/platform is supported.
>>>
>>> [1] http://valgrind.org/
>>> [2] http://valgrind.org/docs/manual/cl-manual.html
>> My question was more related to gcc -pg, gprof & Co.
>>
> Sorry forgot to mention that,
> you can use IMAGE_FEATURES += "dev-pkgs"
>
Section 5.15 has some interesting tidbits of profiling. There are a few
5,x sections so look at them all the find the profiling one ;)
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-10-22 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 12:58 Profiling binaries? Steffen Sledz
2012-10-22 13:12 ` Samuel Stirtzel
2012-10-22 13:20 ` Steffen Sledz
2012-10-22 13:23 ` Samuel Stirtzel
2012-10-22 13:30 ` Jack Mitchell [this message]
2012-10-22 15:08 ` Samuel Stirtzel
2012-10-22 13:40 ` Richard Purdie
2012-10-22 13:49 ` Phil Blundell
2012-10-22 14:44 ` Mark Hatle
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=50854A83.2050106@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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