From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: Tejun Heo <tj@kernel.org>, Alexander Potapenko <glider@google.com>
Cc: dvyukov@google.com, kcc@google.com, aryabinin@virtuozzo.com,
adech.fo@gmail.com, akpm@linux-foundation.org,
alexander.levin@verizon.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: add ksymbolize.py
Date: Thu, 8 Sep 2016 14:27:16 +0300 [thread overview]
Message-ID: <57D14B14.2060008@gmail.com> (raw)
In-Reply-To: <20160824164042.GA2950@htj.duckdns.org>
On 08/24/2016 07:40 PM, Tejun Heo wrote:
> Hello, Alexander.
>
> On Wed, Aug 24, 2016 at 06:37:35PM +0200, Alexander Potapenko wrote:
>> Commit the script that symbolizes BUG messages and KASAN error reports
>> by adding file:line information to each stack frame.
>> The script is a copy of
>> https://github.com/google/sanitizers/blob/master/address-sanitizer/tools/kasan_symbolize.py
>> , originally written by Andrey Konovalov.
>
> I really like the idea of having the script in the tree but can you
> please be more detailed in the patch description (and possibly in the
> help message of the tool)? e.g. describe what it can do and show some
> examples. It's difficult to tell what the script is about from this
> posting.
I've tried to use the script but had to read the code to understand how
exactly to run it. So I also second that a more verbose help is needed
in the script.
>
> Thanks.
>
next prev parent reply other threads:[~2016-09-08 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 16:37 [PATCH] scripts: add ksymbolize.py Alexander Potapenko
2016-08-24 16:40 ` Tejun Heo
2016-09-08 11:27 ` Nikolay Borisov [this message]
2016-08-24 18:19 ` Levin, Alexander
2016-09-08 9:46 ` Alexander Potapenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57D14B14.2060008@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.