From: balbi@ti•com (Felipe Balbi)
To: linux-arm-kernel@lists•infradead.org
Subject: perf not capturing stack traces
Date: Fri, 23 Jan 2015 13:53:40 -0600 [thread overview]
Message-ID: <20150123195340.GF26557@saruman.tx.rr.com> (raw)
In-Reply-To: <20150123195128.GE26557@saruman.tx.rr.com>
Hi,
On Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi wrote:
> Hi,
>
> I'm using v3.19-rc5 on an ARM Cortex A9 board. Unfortunately, perf is
> not able to capture any stack traces even though I CONFIG_STACKTRACE,
> CONFIG_FRAME_POINTER and CONFIG_ARM_UNWIND all enabled.
>
> I wonder if anybody else is facing similar issues.
>
> Here's console grab:
perf features:
Auto-detecting system features:
... dwarf: [ on ]
... glibc: [ on ]
... gtk2: [ OFF ]
... libaudit: [ on ]
... libbfd: [ on ]
... libelf: [ on ]
... libnuma: [ OFF ]
... libperl: [ on ]
... libpython: [ on ]
... libslang: [ on ]
... libunwind: [ on ]
... libdw-dwarf-unwind: [ on ]
... zlib: [ on ]
... DWARF post unwind library: libunwind
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150123/b040cf76/attachment.sig>
next prev parent reply other threads:[~2015-01-23 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 19:51 perf not capturing stack traces Felipe Balbi
2015-01-23 19:53 ` Felipe Balbi [this message]
2015-01-23 20:59 ` Arnaldo Carvalho de Melo
2015-01-23 22:37 ` Felipe Balbi
2015-01-24 15:12 ` Arnaldo Carvalho de Melo
2015-01-24 22:23 ` Felipe Balbi
2015-01-25 15:56 ` Russell King - ARM Linux
2015-01-26 10:27 ` Will Deacon
2015-01-26 12:12 ` Arnaldo Carvalho de Melo
2015-01-26 12:16 ` Will Deacon
2015-01-26 12:29 ` Arnaldo Carvalho de Melo
2015-01-26 13:54 ` Russell King - ARM Linux
2015-01-26 14:33 ` Arnaldo Carvalho de Melo
2015-01-26 13:51 ` Russell King - ARM Linux
2015-01-26 14:37 ` Arnaldo Carvalho de Melo
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=20150123195340.GF26557@saruman.tx.rr.com \
--to=balbi@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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