From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rabin Vincent <rabin@rab.in>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Vince Weaver <vincent.weaver@maine.edu>,
LKML <linux-kernel@vger.kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>, Kees Cook <keescook@chromium.org>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [PATCH v3] scripts: add script for translating stack dump function
Date: Mon, 19 Sep 2016 16:07:32 -0500 [thread overview]
Message-ID: <20160919210732.youtya5lgfd44dkb@treble> (raw)
In-Reply-To: <CA+55aFynG0UDZu56k6yp_yrb2Vo+sc4dZiHBx69M83X4cu0MFg@mail.gmail.com>
On Mon, Sep 19, 2016 at 02:02:18PM -0700, Linus Torvalds wrote:
> On Mon, Sep 19, 2016 at 1:56 PM, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> > On Mon, Sep 19, 2016 at 01:24:03PM -0700, Linus Torvalds wrote:
> >>
> >> because I certainly hope there is always a space there.
> >
> > No luck. The Japanese translation uses an empty string:
>
> Heh.
>
> Ok, we don't want to *just* have the "./" pattern ever be replaced,
> because for all I know there could be a directory name ending with "."
> in there somewhere.
>
> But I guess we could do it this way instead:
>
> --- a/scripts/faddr2line
> +++ b/scripts/faddr2line
> @@ -79,7 +79,7 @@ find_dir_prefix() {
> return
> fi
>
> - DIR_PREFIX=$prefix
> + DIR_PREFIX="$prefix\(\./\)*"
> return 0
> }
>
> and thus just make it part of the auto-generated pattern string instead.
Actually, false alarm. The empty translation string seems to mean "use
the original string":
$ export LANG=ja_JP.utf8
$ ./scripts/faddr2line ~/k/vmlinux type_show+0x10/45
type_show+0x10/0x2d:
type_show at drivers/video/backlight/backlight.c:213
So your previous patch which checks for a space looks good after all :-)
--
Josh
next prev parent reply other threads:[~2016-09-19 21:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 2:43 perf: perf_fuzzer lockup in perf_cgroup_attach Vince Weaver
2016-09-15 5:35 ` Stephane Eranian
2016-09-15 7:24 ` Peter Zijlstra
2016-09-15 12:10 ` Josh Poimboeuf
2016-09-16 14:48 ` [PATCH] scripts: add script for translating stack dump function offsets Josh Poimboeuf
2016-09-16 18:12 ` Linus Torvalds
2016-09-16 19:17 ` Josh Poimboeuf
2016-09-16 19:26 ` Linus Torvalds
2016-09-16 21:26 ` [PATCH v2] " Josh Poimboeuf
2016-09-17 0:09 ` Linus Torvalds
2016-09-17 0:42 ` Josh Poimboeuf
2016-09-17 1:59 ` Linus Torvalds
2016-09-17 2:31 ` Linus Torvalds
2016-09-17 18:45 ` Josh Poimboeuf
2016-09-19 15:52 ` [PATCH v3] scripts: add script for translating stack dump function Josh Poimboeuf
2016-09-19 18:56 ` Linus Torvalds
2016-09-19 19:15 ` Linus Torvalds
2016-09-19 19:28 ` Josh Poimboeuf
2016-09-19 20:00 ` Rabin Vincent
2016-09-19 20:24 ` Linus Torvalds
2016-09-19 20:56 ` Josh Poimboeuf
2016-09-19 21:02 ` Linus Torvalds
2016-09-19 21:07 ` Josh Poimboeuf [this message]
2016-09-17 1:25 ` [PATCH v2] scripts: add script for translating stack dump function offsets Peter Zijlstra
2016-09-17 8:15 ` Rabin Vincent
2016-09-17 18:48 ` Josh Poimboeuf
2016-09-17 9:11 ` [PATCH] " Vegard Nossum
2016-09-17 18:54 ` Josh Poimboeuf
2016-09-15 12:47 ` perf: perf_fuzzer lockup in perf_cgroup_attach Vince Weaver
2016-09-15 7:15 ` Peter Zijlstra
2016-09-15 12:41 ` Vince Weaver
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=20160919210732.youtya5lgfd44dkb@treble \
--to=jpoimboe@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rabin@rab.in \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®