From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: David Carrillo-Cisneros <davidcc@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>, Simon Que <sque@chromium.org>,
Wang Nan <wangnan0@huawei.com>, Jiri Olsa <jolsa@kernel.org>,
Stephane Eranian <eranian@google.com>,
Paul Turner <pjt@google.com>,
kernel-team@lge.com
Subject: Re: [PATCH] perf tool sort: Use default sort if evlist is empty
Date: Mon, 24 Jul 2017 09:47:29 +0200 [thread overview]
Message-ID: <20170724074729.GD8645@krava> (raw)
In-Reply-To: <20170722230949.GB2559@danjae.aot.lge.com>
On Sun, Jul 23, 2017 at 08:09:49AM +0900, Namhyung Kim wrote:
SNIP
> > > also I've got another crash for (added -a option for above example):
> > >
> > > [root@krava perf]# ./perf record -e 'sched:sched_switch' -a sleep 1 | ./perf report
> > > # To display the perf.data header info, please use --header/--header-only options.
> > > #
> > > [ perf record: Woken up 1 times to write data ]
> > > [ perf record: Captured and wrote 0.000 MB (null) ]
> > > Segmentation fault (core dumped)
> > >
> > > catchsegv got:
> > > /home/jolsa/kernel/linux-perf/tools/perf/util/ordered-events.c:85(free_dup_event)[0x51a6a5]
> > > ./perf(ordered_events__free+0x5c)[0x51b0b7]
> > > /home/jolsa/kernel/linux-perf/tools/perf/util/session.c:1751(__perf_session__process_pipe_events)[0x518abb]
> > > ./perf(perf_session__process_events+0x91)[0x5190f0]
> > > /home/jolsa/kernel/linux-perf/tools/perf/builtin-report.c:598(__cmd_report)[0x443a91]
> > > ./perf(cmd_report+0x169b)[0x4455a3]
> > > /home/jolsa/kernel/linux-perf/tools/perf/perf.c:296(run_builtin)[0x4be1b0]
> > > /home/jolsa/kernel/linux-perf/tools/perf/perf.c:348(handle_internal_command)[0x4be41d]
> > > /home/jolsa/kernel/linux-perf/tools/perf/perf.c:395(run_argv)[0x4be56f]
> > > ./perf(main+0x2d6)[0x4be949]
> > > /lib64/libc.so.6(__libc_start_main+0xf1)[0x7f3de8a10401]
> > > ./perf(_start+0x2a)[0x42831a]
> > >
> > > looks like some mem corruption.. will try to follow up
> > > on this later if nobody beats me to it ;-)
> >
> > Cannot reproduce it in acme's perf/core building the tool with
> > make NO_LIBPYTHON=1 LDFLAGS=-static
> >
> > If you have a file with the perf record output causing perf report's
> > crash, I'd like to take a look.
hm, I can't reproduce any longer.. :-\
jirka
next prev parent reply other threads:[~2017-07-24 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 5:11 [PATCH] perf tool sort: Use default sort if evlist is empty David Carrillo-Cisneros
2017-07-21 7:44 ` Jiri Olsa
2017-07-21 20:02 ` David Carrillo-Cisneros
2017-07-22 23:09 ` Namhyung Kim
2017-07-24 7:47 ` Jiri Olsa [this message]
2017-07-24 10:43 ` David Carrillo-Cisneros
2017-07-26 20:03 ` Arnaldo Carvalho de Melo
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=20170724074729.GD8645@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pjt@google.com \
--cc=sque@chromium.org \
--cc=wangnan0@huawei.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