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 18:47:43 +0200 [thread overview]
Message-ID: <20181009164743.GA22886@krava> (raw)
In-Reply-To: <CAO49afLqUGuBi_R7BKyojqnkHrMGqXquy-FdVFscOu6Ez0cVFw@mail.gmail.com>
On Tue, Oct 09, 2018 at 11:27:04AM -0500, Anthony LaTorre wrote:
> Hi,
>
> I'm currently running Linux kernel 4.18.10-100.fc27.x86_64 and have a
> problem profiling a program that used to work. Currently when I
> profile the program with the following command:
>
> $ perf record -F 99 -p PID --call-graph dwarf sleep 10
>
> it produces a data file which causes perf report to segfault:
>
> $ perf report
> perf: Segmentation fault
> -------- backtrace --------
> perf(+0x325302)[0x55860ae79302]
> /lib64/libc.so.6(+0x347d0)[0x7fbc8f3987d0]
> perf(+0x273e80)[0x55860adc7e80]
> perf(unwind__get_entries+0x1d9)[0x55860ae4ace9]
> perf(thread__resolve_callchain+0xfd)[0x55860adce7dd]
> perf(sample__resolve_callchain+0x58)[0x55860adc45b8]
> perf(hist_entry_iter__add+0x98)[0x55860adfa908]
> perf(+0x1ab8d9)[0x55860acff8d9]
> perf(+0x280603)[0x55860add4603]
> perf(+0x283c63)[0x55860add7c63]
> perf(+0x280e04)[0x55860add4e04]
> perf(perf_session__process_events+0x8ae)[0x55860add6bee]
> perf(cmd_report+0x190f)[0x55860ad01a4f]
> perf(+0x21a961)[0x55860ad6e961]
> perf(+0x21ac6e)[0x55860ad6ec6e]
> perf(main+0x361)[0x55860ace8411]
> /lib64/libc.so.6(__libc_start_main+0xea)[0x7fbc8f384fea]
> perf(_start+0x2a)[0x55860ace889a]
>
> I've attached the data file which is causing the issue.
>
> The perf version is:
>
> $ perf --version
> perf version 4.18.10
>
> and I'm running Fedora 27 if that makes a difference.
>
> I've tried to reproduce with simpler programs so I could send a
> minimal working example, but it doesn't appear to cause the issue.
please do, I can't reproduce this
thanks,
jirka
next parent reply other threads:[~2018-10-09 16:47 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 ` Jiri Olsa [this message]
2018-10-09 18:54 ` perf report segfault Anthony LaTorre
2018-10-09 20:18 ` Anthony LaTorre
2018-10-09 21:41 ` Jiri Olsa
[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=20181009164743.GA22886@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.