From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tool: Ensure forward progress unwinding frames
Date: Mon, 9 Dec 2013 15:16:24 +0100 [thread overview]
Message-ID: <20131209141624.GC30360@krava.brq.redhat.com> (raw)
In-Reply-To: <52A5CE1B.3030007@gmail.com>
On Mon, Dec 09, 2013 at 07:05:15AM -0700, David Ahern wrote:
> On 12/9/13, 3:02 AM, Jiri Olsa wrote:
> >>On 12/1/13, 5:01 PM, David Ahern wrote:
> >>>The dwarf option for callstacks is getting stuck on the unwind and showing
> >>>repeated frames. For example,
> >>>
> >>>qemu-system-x86 13759 [001] 287663.084957: syscalls:sys_enter_futex: uaddr: 0x7f770a958700, op: 0x00000081, val: 0x00000001, utime: 0x7f75ea
> >>> 7f7705fd23ea __lll_unlock_wake (/lib64/libpthread-2.14.90.so)
> >>> 7f7705fcf045 _L_unlock_649 (/lib64/libpthread-2.14.90.so)
> >>> 7f7705fcf045 _L_unlock_649 (/lib64/libpthread-2.14.90.so)
> >>> 7f7705fcf045 _L_unlock_649 (/lib64/libpthread-2.14.90.so)
> >>> 7f7705fcf045 _L_unlock_649 (/lib64/libpthread-2.14.90.so)
> >>> 7f7705fcf045 _L_unlock_649 (/lib64/libpthread-2.14.90.so)
> >>> ...
> >
> >I wonder this is us or libunwind bug (or cfi code) ;-)
> >
> >looks like you can reproduce..? are you using the latest libunwind?
>
> $ rpm -q libunwind
> libunwind-0.99-2.20110424git1e10c293.fc16.x86_64
[jolsa@krava libunwind]$ rpm -q libunwind
libunwind-1.1-2.fc19.x86_64
;-)
prev parent reply other threads:[~2013-12-09 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 0:01 David Ahern
2013-12-08 17:46 ` David Ahern
2013-12-09 10:02 ` Jiri Olsa
2013-12-09 14:05 ` David Ahern
2013-12-09 14:16 ` Jiri Olsa [this message]
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=20131209141624.GC30360@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome