[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18594a2a-553a-c2b8-2c4f-6f7563ae3727@linux.intel.com>
Date: Fri, 16 Dec 2022 09:24:54 +0200
From: Andi Kleen <ak@...ux.intel.com>
To: Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-perf-users@...r.kernel.org,
Milian Wolff <milian.wolff@...b.com>,
Leo Yan <leo.yan@...aro.org>
Subject: Re: [PATCH 2/9] perf report: Ignore SIGPIPE for srcline
On 12/15/2022 9:28 PM, Namhyung Kim wrote:
> It can get SIGPIPE when it uses an external addr2line process and the
> process was terminated unexpectedly. Let's ignore the signal and move
> on to the next sample. The sample will get the default srcline value
> anyway.
That's a bit dangerous -- if perf report output is piped to something
else you really want to stop on SIGPIPE.
You would need to find a way to distinguish those cases.
-Andi
Powered by blists - more mailing lists