From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: perf stat crashes with latest download (git clone -b perf/core)
Date: Thu, 9 Nov 2017 11:31:42 -0300 [thread overview]
Message-ID: <20171109143142.GL4333@kernel.org> (raw)
In-Reply-To: <20171109143024.GK4333@kernel.org>
Em Thu, Nov 09, 2017 at 11:30:24AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Nov 09, 2017 at 03:23:43PM +0100, Thomas-Mich Richter escreveu:
> > I have downloaded this code some days ago
> >
> > git clone -b perf/core git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux acme
> >
> > and run into this issue which I reproduce on my KVM virtual machine on intel and s390x.
> >
> > [root@localhost perf]# ./perf stat -e '{cpu-clock,instructions}' kill
> > kill: not enough arguments
> > Segmentation fault (core dumped)
> > [root@localhost perf]#
> >
> > When I debug this further using gdb I get this error:
>
> Trying with today's acme/perf/core:
>
> Yeah,
>
> [acme@jouet linuxdev-br]$ perf stat -e '{cpu-clock,instructions}' kill
> kill: not enough arguments
> Segmentation fault (core dumped)
> [acme@jouet linuxdev-br]$
>
> Trying to bisect it now, thanks for the report!
Additional data point, this is happening only with perf/core, not
perf/urgent.
- Arnaldo
prev parent reply other threads:[~2017-11-09 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:23 perf stat crashes with latest download (git clone -b perf/core) Thomas-Mich Richter
2017-11-09 14:30 ` Arnaldo Carvalho de Melo
2017-11-09 14:31 ` Arnaldo Carvalho de Melo [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=20171109143142.GL4333@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=tmricht@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).