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]
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: 0x0081, val
On Sun, Dec 08, 2013 at 10:46:13AM -0700, David Ahern wrote:
> ping.. Jiri, any thoughts on this?
oops, missed that.. sry
>
> 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-
ping.. Jiri, any thoughts on this?
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: 0x0081, val: 0
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: 0x0081, val: 0x0001, utime: 0x7f75ea
7f7705fd23ea __lll_unlock_wake (/lib64/
5 matches
Mail list logo