[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131209141624.GC30360@krava.brq.redhat.com>
Date: Mon, 9 Dec 2013 15:16:24 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: David Ahern <dsahern@...il.com>
Cc: acme@...stprotocols.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf tool: Ensure forward progress unwinding frames
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@...va libunwind]$ rpm -q libunwind
libunwind-1.1-2.fc19.x86_64
;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists