From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: profiling howto?
Date: Wed, 02 Feb 2011 13:59:25 +0100 [thread overview]
Message-ID: <4D49552D.3010705@dresearch.de> (raw)
In-Reply-To: <4D4929CB.6040009@dresearch.de>
Am 02.02.2011 10:54, schrieb Steffen Sledz:
> Has anybody some instructions/hints how to enable profiling
> support for selected libs and/or binaries in OE?
The local.conf.sample does contain this section:
# Uncomment these to build a package such that you can use gprof to profile it.
# NOTE: This will only work with 'linux' targets, not
# 'linux-uclibc', as uClibc doesn't provide the necessary
# object files. Also, don't build glibc itself with these
# flags, or it'll fail to build.
#
# PROFILE_OPTIMIZATION = "-pg"
# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"
# LDFLAGS =+ "-pg"
This seems to do the work for the complete image.
But is it possible to enable profiling for selected libs and/or binaries only?
Steffen
next prev parent reply other threads:[~2011-02-02 13:00 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 [this message]
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
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=4D49552D.3010705@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@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