linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jean.pihet@linaro.org (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present
Date: Thu, 5 Sep 2013 17:29:48 +0200	[thread overview]
Message-ID: <CAFrcx1=V7zRuK767RHCXbu99Mtf+VZrmv7_4mOn7Kb6B8cd2sQ@mail.gmail.com> (raw)
In-Reply-To: <CAFrcx1koLAnNRBtpAhOoTP0SC-wWknY7ipUmcvnjxKqwDOUmag@mail.gmail.com>

Hi,

On 5 September 2013 15:33, Jean Pihet <jean.pihet@linaro.org> wrote:
> On 5 September 2013 15:19, Will Deacon <will.deacon@arm.com> wrote:
>> On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
>>> On 5 September 2013 15:05, Jean Pihet <jean.pihet@newoldbits.com> wrote:
>>> [..]
>>> > Here are the commands I have been using:
>>> >  perf record -g dwarf -- <binary to profile>
>>> >  perf report --sort symbol --call-graph --stdio
>>> >
>>>
>>> Ah, I failed to add the 'dwarf' after -g, however, in that case, my
>>> perf report segfaults:
>>
>> Same SEGV here.
> Ouch! I never got the segfault on my side.

The segfault is caused by libunwind. With the latest version [1],
dwarf unwinding works fine.
Investigation on-going, more to come!

[1] git://git.sv.gnu.org/libunwind.git

Regards,
Jean

>
> Here is the setup I am using:
> - OMAP4 Pandaboard,
> - 13.07 Ubuntu dist from http://www.linaro.org/downloads/,
> - 3.11 mainline kernel + 3 patches for unwinding info,
> - patched perf tool,
> - dbg flavor of the libs installed. Without them installed I do not
> get the address resolved but no segfaults
>
> Can you check if the linked libraries contain the .debug_frame
> sections? (ldd; readelf -S /lib/arm-linux-gnueabihf/libc-2.17.so|grep
> debug_frame; readelf -S
> /usr/lib/debug/lib/arm-linux-gnueabihf/libc-2.17.so|grep debug_frame)?
>
>>
>> Will
>
> Jean

  reply	other threads:[~2013-09-05 15:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 18:04 [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-04 18:04 ` [PATCH 1/3] ARM: perf: add support for perf regs API Jean Pihet
2013-09-05 13:21   ` Ard Biesheuvel
2013-09-04 18:04 ` [PATCH 2/3] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-04 18:04 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-05 12:45   ` Will Deacon
2013-09-05 13:05     ` Jean Pihet
2013-09-05 13:17       ` Ard Biesheuvel
2013-09-05 13:19         ` Will Deacon
2013-09-05 13:33           ` Jean Pihet
2013-09-05 15:29             ` Jean Pihet [this message]
2013-09-05 15:45               ` Ard Biesheuvel
2013-09-05 13:10     ` Ard Biesheuvel
2013-09-05 16:30   ` Jiri Olsa
2013-09-05 16:49     ` Jean Pihet
2013-09-06 10:17       ` Jiri Olsa
2013-09-06  9:31     ` Jean Pihet
2013-09-06 10:17       ` Jiri Olsa
2013-09-06 14:10         ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2013-09-09 10:00 [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-09 10:00 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-10 19:14   ` David Ahern
2013-09-10 19:38     ` Jean Pihet
2013-09-12 12:38   ` Jiri Olsa

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='CAFrcx1=V7zRuK767RHCXbu99Mtf+VZrmv7_4mOn7Kb6B8cd2sQ@mail.gmail.com' \
    --to=jean.pihet@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).