[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161662453186.3012082.16246196278552144536@swboyd.mtv.corp.google.com>
Date: Wed, 24 Mar 2021 15:22:11 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jiri Olsa <jolsa@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Jessica Yu <jeyu@...nel.org>,
Evan Green <evgreen@...omium.org>,
Hsin-Yi Wang <hsinyi@...omium.org>,
Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
Sasha Levin <sashal@...nel.org>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH v2 07/12] scripts/decode_stacktrace.sh: Support debuginfod
Quoting Andy Shevchenko (2021-03-24 04:27:53)
> On Tue, Mar 23, 2021 at 07:04:38PM -0700, Stephen Boyd wrote:
> > Now that stacktraces contain the build ID information we can update this
> > script to use debuginfod-find to locate the debuginfo for the vmlinux
> > and modules automatically. This can replace the existing code that
> > requires specifying a path to vmlinux or tries to find the vmlinux and
> > modules automatically by using the release number. Work it into the
> > script as a fallback option if the vmlinux isn't specified on the
> > commandline.
>
> One wish for the shell scripts: try to avoid bashisms as much as possible,
> please.
>
I wish too but the script has /bin/bash at the start and I was trying to
follow similar style to what was already in here. Feel free to send a
patch to remove the bashisms.
Powered by blists - more mailing lists