[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP-5=fXx78Mq+rCv78V_tm7FY-aEqKzBT79GZ5gTCw5-3vLp9g@mail.gmail.com>
Date: Fri, 20 Dec 2024 10:59:28 -0800
From: Ian Rogers <irogers@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, John Garry <john.g.garry@...cle.com>,
Sandipan Das <sandipan.das@....com>, Benjamin Gray <bgray@...ux.ibm.com>, Xu Yang <xu.yang_2@....com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH v1] perf jevents: Provide better path information for
broken json
On Thu, Nov 14, 2024 at 9:23 AM Ian Rogers <irogers@...gle.com> wrote:
>
> If the json input to jevents.py is broken it can be problematic to
> work out which particular json file is broken. When processing files
> catch exceptions that occur that re-raise the exception with path
> details added.
>
> Signed-off-by: Ian Rogers <irogers@...gle.com>
Ping.
Thanks,
Ian
Powered by blists - more mailing lists