From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [BUG] perf report: segfault with --no-group in pipe mode
Date: Sat, 3 Aug 2019 10:45:20 +0200 [thread overview]
Message-ID: <20190803084520.GA1008@krava> (raw)
In-Reply-To: <CABPqkBQtnYM6E2F3JiZ2A5z8iR+MvxM5DH4L6KyAeSaBfnGEPw@mail.gmail.com>
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
prev parent reply other threads:[~2019-08-03 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 16:38 [BUG] perf report: segfault with --no-group in pipe mode Stephane Eranian
2019-08-03 8:45 ` 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=20190803084520.GA1008@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=eranian@google.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