Re: [PATCH 1/2] perf script: allow extended console debug output

From: Jiri Olsa
Date: Mon Oct 22 2018 - 05:40:39 EST


On Sun, Oct 21, 2018 at 09:14:23PM +0200, Milian Wolff wrote:
> The script tool isn't using a browser, yet use_browser
> wasn't set explicitly to zero. This in turn lead to confusing
> output such as:
>
> ```
> $ perf script -vvv ...
> ...
> overlapping maps in /home/milian/foobar (disable tui for more info)
> ...
> ```
>
> Explicitly set use_browser to 0 now, which gives us the extended
> debug information now in perf script as expected.
>
> Signed-off-by: Milian Wolff <milian.wolff@xxxxxxxx>
> Cc: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>

Acked-by: Jiri Olsa <jolsa@xxxxxxxxxx>

thanks,
jirka

> ---
> tools/perf/builtin-script.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> index 4da5e32b9e03..bd468b90801b 100644
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
> @@ -3417,8 +3417,10 @@ int cmd_script(int argc, const char **argv)
> exit(-1);
> }
>
> - if (!script_name)
> + if (!script_name) {
> setup_pager();
> + use_browser = 0;
> + }
>
> session = perf_session__new(&data, false, &script.tool);
> if (session == NULL)
> --
> 2.19.1