From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Generating Debug Info Files
Date: Thu, 14 May 2015 21:59:14 +0200 [thread overview]
Message-ID: <20150514215914.10e83cad@free-electrons.com> (raw)
In-Reply-To: <00b501d08d9b$87eae570$97c0b050$@osullivan@cloudiumsystems.com>
Dear John OSullivan,
On Wed, 13 May 2015 17:40:31 +0100, John OSullivan wrote:
> When I run perf on my buildroot based system it complains about missing
> symbols for my libraries and applications. I know it is possible to generate
> binaries with symbolic information in the staging area by selecting 'build
> packages with debugging symbols', but is there any way of generating
> separate .debug type files or do I need to do this in postBuild with a
> script based on objcopy.
No, we don't have support for separate .debug files currently.
But how would it work exactly, since perf is running on the target?
Don't you simply need to have debugging symbols on the target? If
that's the case, you can simply do BR2_ENABLE_DEBUG=y and
BR2_strip_none=y.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-14 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 16:40 [Buildroot] Generating Debug Info Files John OSullivan
2015-05-14 19:59 ` Thomas Petazzoni [this message]
2015-05-15 11:05 ` John OSullivan
2015-05-15 13:12 ` Thomas Petazzoni
2015-05-15 15:46 ` John O'Sullivan
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=20150514215914.10e83cad@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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