[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191004023535.3ddpkym64xb2cvvl@mail.google.com>
Date: Fri, 4 Oct 2019 10:35:37 +0800
From: Changbin Du <changbin.du@...il.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Changbin Du <changbin.du@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] perf: add support for logging debug messages to
file
On Sun, Sep 29, 2019 at 09:44:07AM +0200, Jiri Olsa wrote:
> On Sun, Sep 22, 2019 at 10:38:21AM +0800, Changbin Du wrote:
> > When in TUI mode, it is impossible to show all the debug messages to
> > console. This make it hard to debug perf issues using debug messages.
> > This patch adds support for logging debug messages to file to resolve
> > this problem.
> >
> > v2:
> > o specific all debug options one time.
> >
> > Changbin Du (2):
> > perf: support multiple debug options separated by ','
> > perf: add support for logging debug messages to file
>
> hi,
> getting segfault with:
>
> [jolsa@...va perf]$ ./perf --debug verbose=2,file report
> build id event received for [kernel.kallsyms]: bf6ca14c03795fd67b4d88113681ba4af2b8c18a
> Segmentation fault (core dumped)
>
Hmm, this because the va_list variable cannot be used twice. I resolve this by
making stderr and file options exclusive.
> jirka
>
> >
> > tools/perf/Documentation/perf.txt | 14 ++--
> > tools/perf/util/debug.c | 106 ++++++++++++++++++------------
> > 2 files changed, 73 insertions(+), 47 deletions(-)
> >
> > --
> > 2.20.1
> >
--
Cheers,
Changbin Du
Powered by blists - more mailing lists