[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <e4396e01-2de9-3c11-7a2f-5e7fc894b5ae@linux.ibm.com>
Date: Wed, 20 Jun 2018 19:30:50 +0530
From: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: jolsa@...hat.com, alexander.shishkin@...ux.intel.com,
namhyung@...nel.org, dsahern@...il.com, davidcc@...gle.com,
ak@...ux.intel.com, yao.jin@...ux.intel.com,
linux-kernel@...r.kernel.org,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
Subject: Re: [PATCH 2/3] perf script: Fix crash because of missing evsel->priv
Hi Arnaldo,
On 06/20/2018 07:22 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jun 20, 2018 at 07:00:29PM +0530, Ravi Bangoria escreveu:
>> perf script in pipped mode is crashing because evsel->priv is not
>> set properly. Fix it.
>>
>> Before:
>> # ./perf record -o - -- ls | ./perf script
>> Segmentation fault (core dumped)
>>
>> After:
>> # ./perf record -o - -- ls | ./perf script
>> ls 2282 1031.731974: 250000 cpu-clock:uhH: 7effe4b3d29e
>> ls 2282 1031.732222: 250000 cpu-clock:uhH: 7effe4b3a650
>>
>> Signed-off-by: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
>> Fixes: a14390fde64e ("perf script: Allow creating per-event dump files")
>
> Humm, this cset doesn't set evsel->priv to a 'struct perf_evsel_script'
> object, will check which one does to continue review.
Possible. Actually, git bisect led me to this commit.
Ravi
Powered by blists - more mailing lists