Re: [BUG] perf annotate: broken in pipe mode

2013-02-01 Thread Stephane Eranian
On Fri, Feb 1, 2013 at 9:04 AM, Namhyung Kim wrote: > Hi Stephane, > > On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote: >> Hi, >> >> Looks like perf annotate in pipe mode is totally broken nowadays. >> I tried this from tip.git: >> >> $ perf record -o - noploop 5 >perf.data >> $ perf

Re: [BUG] perf annotate: broken in pipe mode

2013-02-01 Thread Namhyung Kim
Hi Stephane, On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote: > Hi, > > Looks like perf annotate in pipe mode is totally broken nowadays. > I tried this from tip.git: > > $ perf record -o - noploop 5 >perf.data > $ perf annotate -i i < perf.data > Core dump > > Callstack looks as

Re: [BUG] perf annotate: broken in pipe mode

2013-02-01 Thread Namhyung Kim
Hi Stephane, On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote: Hi, Looks like perf annotate in pipe mode is totally broken nowadays. I tried this from tip.git: $ perf record -o - noploop 5 perf.data $ perf annotate -i i perf.data Core dump Callstack looks as follows:

Re: [BUG] perf annotate: broken in pipe mode

2013-02-01 Thread Stephane Eranian
On Fri, Feb 1, 2013 at 9:04 AM, Namhyung Kim namhy...@kernel.org wrote: Hi Stephane, On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote: Hi, Looks like perf annotate in pipe mode is totally broken nowadays. I tried this from tip.git: $ perf record -o - noploop 5 perf.data $ perf

[BUG] perf annotate: broken in pipe mode

2013-01-31 Thread Stephane Eranian
Hi, Looks like perf annotate in pipe mode is totally broken nowadays. I tried this from tip.git: $ perf record -o - noploop 5 >perf.data $ perf annotate -i i < perf.data Core dump Callstack looks as follows: 0x0049f9e4 in add_hist_entry (hists=0x809708, entry=0x7fffde60,

[BUG] perf annotate: broken in pipe mode

2013-01-31 Thread Stephane Eranian
Hi, Looks like perf annotate in pipe mode is totally broken nowadays. I tried this from tip.git: $ perf record -o - noploop 5 perf.data $ perf annotate -i i perf.data Core dump Callstack looks as follows: 0x0049f9e4 in add_hist_entry (hists=0x809708, entry=0x7fffde60,