2019-08-03 15:40:14

by Stephane Eranian

Subject: [BUG] perf report: segfault with --no-group in pipe mode

Hi,

When trying the following command line with perf from tip,git, I got:

$ perf record --group -c 100000 -e '{branch-misses,branches}' -a -o -
sleep 1| perf report --no-group -F sample,cpu,period -i -
# To display the perf.data header info, please use
--header/--header-only options.
#
Segmentation fault (core dumped)

(gdb) r report --no-group -F sample,cpu,period -i - < tt
Starting program: /export/hda3/perftest/perf.tip report --no-group -F
sample,cpu,period -i - < tt
# To display the perf.data header info, please use
--header/--header-only options.
#

Program received signal SIGSEGV, Segmentation fault.
hlist_add_head (h=0xeb9ed8, n=0xebdfd0) at
/usr/local/google/home/eranian/G/bnw.tip/tools/include/linux/list.h:644
644 /usr/local/google/home/eranian/G/bnw.tip/tools/include/linux/list.h:
No such file or directory.
(gdb)

Can you reproduce this?
Thanks.

2019-08-04 03:38:23

by Jiri Olsa

Subject: Re: [BUG] perf report: segfault with --no-group in pipe mode

On Fri, Aug 02, 2019 at 09:38:49AM -0700, Stephane Eranian wrote:
> Hi,
>
> When trying the following command line with perf from tip,git, I got:
>
> $ perf record --group -c 100000 -e '{branch-misses,branches}' -a -o -
> sleep 1| perf report --no-group -F sample,cpu,period -i -
> # To display the perf.data header info, please use
> --header/--header-only options.
> #
> Segmentation fault (core dumped)
>
> (gdb) r report --no-group -F sample,cpu,period -i - < tt
> Starting program: /export/hda3/perftest/perf.tip report --no-group -F
> sample,cpu,period -i - < tt
> # To display the perf.data header info, please use
> --header/--header-only options.
> #
>
> Program received signal SIGSEGV, Segmentation fault.
> hlist_add_head (h=0xeb9ed8, n=0xebdfd0) at
> /usr/local/google/home/eranian/G/bnw.tip/tools/include/linux/list.h:644
> 644 /usr/local/google/home/eranian/G/bnw.tip/tools/include/linux/list.h:
> No such file or directory.
> (gdb)
>
> Can you reproduce this?

hi,
looks like it's you might be hitting this one:
79b2fe5e7561 perf tools: Fix proper buffer size for feature processing

please try Arnaldo's perf/urgent, it's in there

jirka