Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Generating Debug Info Files
Date: Fri, 15 May 2015 15:12:18 +0200	[thread overview]
Message-ID: <20150515151218.2cb0d3e4@free-electrons.com> (raw)
In-Reply-To: <5555D2F5.80308@cloudiumsystems.com>

Dear John OSullivan,

On Fri, 15 May 2015 12:05:25 +0100, John OSullivan wrote:

> Thanks for your reply, I already have debugging symbols on for the test 
> application running on my target but perf still complains:
> Failed to open test_application, continuing without symbols

Ok.

> The file has symbols and is not stripped and gdb has no problem finding 
> the symbols so I think the issue is that perf is expecting to find the 
> symbols in some separate file, its difficult to get clarity on this but 
> I believe that in Ubuntu you would install a debug package, I believe 
> this installs separate files with symbol information in certain 
> locations like for example /usr/lib/.debug for libraries.
> I was going to try and do something similar with my buildroot file 
> system to see if it resolved the perf problem.

I am not sure that having the debugging symbols in a separate file
makes a difference here. It's indeed the way desktop/server distros
such as Ubuntu distribute the debugging symbols, but I 'm not sure it
will make a difference for perf.

Maybe perf needs some dependency such as libunwind to be able to use
the debugging symbols?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-05-15 13:12 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
2015-05-15 11:05   ` John OSullivan
2015-05-15 13:12     ` Thomas Petazzoni [this message]
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=20150515151218.2cb0d3e4@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