[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v9r6e6gw.fsf@linux.intel.com>
Date: Tue, 26 Nov 2019 12:19:11 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Changbin Du <changbin.du@...il.com>
Cc: Jiri Olsa <jolsa@...hat.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 v7 0/2] perf: add support for logging debug messages to file
Changbin Du <changbin.du@...il.com> writes:
> 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.
This was already solved in
commit f78eaef0e0493f6068777a246b9c4d9d5cf2b7aa
Author: Andi Kleen <ak@...ux.intel.com>
Date: Fri Nov 21 13:38:00 2014 -0800
perf tools: Allow to force redirect pr_debug to stderr.
When debugging the tui browser I find it useful to redirect the
debug
log into a file. Currently it's always forced to the message
line.
Add an option to force it to stderr. Then it can be easily
redirected.
You can do
perf report --debug stderr 2> file ...
-Andi
Powered by blists - more mailing lists