From: John OSullivan <john.osullivan@cloudiumsystems.com>
To: buildroot@busybox.net
Subject: [Buildroot] Generating Debug Info Files
Date: Wed, 13 May 2015 17:40:31 +0100 [thread overview]
Message-ID: <00b501d08d9b$87eae570$97c0b050$@osullivan@cloudiumsystems.com> (raw)
Hi,
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.
Regards
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150513/dc056904/attachment.html>
next reply other threads:[~2015-05-13 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 16:40 John OSullivan [this message]
2015-05-14 19:59 ` [Buildroot] Generating Debug Info Files Thomas Petazzoni
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='00b501d08d9b$87eae570$97c0b050$@osullivan@cloudiumsystems.com' \
--to=john.osullivan@cloudiumsystems.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