From: Bob Cochran <yocto@mindchasers.com>
To: Clemens Eisserer <linuxhippy@gmail.com>, meta-freescale@yoctoproject.org
Subject: Re: How to build/include debug-infos for certain packages?
Date: Wed, 28 Jan 2015 17:53:46 -0500 [thread overview]
Message-ID: <54C9687A.7080107@mindchasers.com> (raw)
In-Reply-To: <CAFvQSYQikgyjsamL0ykdBvR8Fzc7Vni2LEoGYu=6Nm75-+JVsQ@mail.gmail.com>
On 01/28/2015 04:36 PM, Clemens Eisserer wrote:
> Hi,
>
> Using the QorIQ SDK-1.7 on e6500 based hardware we've recently started
> to use oprofile for performance analysis.
> However libraries shipped as part of the SDK are opaque to oprofile,
> because the debug-infos are missing.
>
> Is there any way to include debug-infos of certain packages (such as
> libc and libgcc) in the image - or even better - install it later?
You can add -dbg and -dev packages to your image.
Something like:
IMAGE_INSTALL_append = " libgcc-dev"
You could also install it manually on the target without adding it to
your image if you set up the smart package manager.
>
> Thank you in advanve, Clemens
>
>
prev parent reply other threads:[~2015-01-28 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 21:36 How to build/include debug-infos for certain packages? Clemens Eisserer
2015-01-28 22:53 ` Bob Cochran [this message]
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=54C9687A.7080107@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=linuxhippy@gmail.com \
--cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.