Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Samuel Stirtzel <s.stirtzel@googlemail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Profiling binaries?
Date: Mon, 22 Oct 2012 15:20:26 +0200	[thread overview]
Message-ID: <5085481A.5050909@dresearch-fe.de> (raw)
In-Reply-To: <CAGiJk9dt0OTOMG5T7DoomCfXxp+FUw15PWTXnaCSm=BJOpfjnw@mail.gmail.com>

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.

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058



  reply	other threads:[~2012-10-22 13:33 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 [this message]
2012-10-22 13:23     ` Samuel Stirtzel
2012-10-22 13:30       ` Jack Mitchell
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=5085481A.5050909@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=s.stirtzel@googlemail.com \
    /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