From: Jiri Olsa <jolsa@redhat.com>
To: Anthony LaTorre <tlatorre9@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, jolsa@kernel.org,
acme@kernel.org, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: perf report segfault
Date: Tue, 9 Oct 2018 23:41:58 +0200 [thread overview]
Message-ID: <20181009214158.GB31206@krava> (raw)
In-Reply-To: <CAO49afJVHsywYdosSqceQiMzFdaYivm4kiNnC_+WKq15jsA7Dg@mail.gmail.com>
On Tue, Oct 09, 2018 at 03:18:12PM -0500, Anthony LaTorre wrote:
> Ok, I can reliably reproduce it by profiling the following program:
>
> #include <math.h>
>
> int main(int argc, char **argv)
> {
> int i;
> double sum;
>
> while (1) {
> sum += exp(++i);
> }
>
> return 0;
> }
>
> compiled with:
>
> $ cc -o test test.c -lm
>
> with the following command:
>
> $ perf record -F 99 -p 20016 --call-graph dwarf sleep 10
still nothing.. any chance you could try on latest perf sources?
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
$ cd linux
$ git checkout -b perf/core origin/perf/core
$ cd tools/perf
$ make
$ ./perf ...
you might need some packages mentioned in (search for 'yum install'):
https://perf.wiki.kernel.org/index.php/Jolsa_Howto_Install_Sources
it's little outdated, but the packages lists will do
thanks,
jirka
next prev parent reply other threads:[~2018-10-09 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO49afLqUGuBi_R7BKyojqnkHrMGqXquy-FdVFscOu6Ez0cVFw@mail.gmail.com>
2018-10-09 16:47 ` perf report segfault Jiri Olsa
2018-10-09 18:54 ` Anthony LaTorre
2018-10-09 20:18 ` Anthony LaTorre
2018-10-09 21:41 ` Jiri Olsa [this message]
[not found] ` <CAO49af+5TaWrdYeM3XyHoti0obH--0txq9_a6_9ZPMuB-J=hjg@mail.gmail.com>
2018-10-09 22:19 ` Anthony LaTorre
2018-10-09 22:20 ` Jiri Olsa
2018-10-10 5:43 ` Sandipan Das
2018-10-10 6:19 ` Ingo Molnar
2018-10-10 7:14 ` Jiri Olsa
2018-10-10 12:54 ` Arnaldo Carvalho de Melo
2018-10-09 21:38 ` Jiri Olsa
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=20181009214158.GB31206@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tlatorre9@gmail.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