linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Levin, Alexander" <alexander.levin@verizon.com>
To: Alexander Potapenko <glider@google.com>
Cc: "dvyukov@google.com" <dvyukov@google.com>,
	"kcc@google.com" <kcc@google.com>,
	"aryabinin@virtuozzo.com" <aryabinin@virtuozzo.com>,
	"adech.fo@gmail.com" <adech.fo@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"Levin, Alexander" <alexander.levin@verizon.com>,
	"tj@kernel.org" <tj@kernel.org>,
	"kasan-dev@googlegroups.com" <kasan-dev@googlegroups.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts: add ksymbolize.py
Date: Wed, 24 Aug 2016 14:19:22 -0400	[thread overview]
Message-ID: <20160824181922.GB6842@sasha-lappy> (raw)
In-Reply-To: <1472056655-30791-1-git-send-email-glider@google.com>

On Wed, Aug 24, 2016 at 12:37:35PM -0400, Alexander Potapenko wrote:
> he 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.

So what's the difference between this script and scripts/decode_stacktrace.sh that already lives upstream?


Thanks,
Sasha

  parent reply	other threads:[~2016-08-24 18:20 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
2016-08-24 18:19 ` Levin, Alexander [this message]
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=20160824181922.GB6842@sasha-lappy \
    --to=alexander.levin@verizon.com \
    --cc=adech.fo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).