From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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>
Subject: Re: [PATCH] scripts: add script for translating stack dump function offsets
Date: Sat, 17 Sep 2016 13:54:13 -0500 [thread overview]
Message-ID: <20160917185413.mms2zb3lkmrk6wy5@treble> (raw)
In-Reply-To: <CAOMGZ=Fcwsx0C4HmjbPCLbc67JvA-cpO-0bU3HxqYabROJOLwA@mail.gmail.com>
On Sat, Sep 17, 2016 at 11:11:44AM +0200, Vegard Nossum wrote:
> On 16 September 2016 at 21:17, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> > On Fri, Sep 16, 2016 at 11:12:10AM -0700, Linus Torvalds wrote:
> >> Side note: I find addr2line almost completely useless in many cases
> >> not because of address space randomization, but because of how complex
> >> the inlining often is. I just had something where I decided to use
> >> addr2line and it just pointed me to the __read_once_size_nocheck()
> >> line in <linux/compiler.h>. That was not very useful.
> >>
> >> I ended up actually looking at the instructions *around* it, to find
> >> where that one instruction had been inlined from.
> >>
> >> So I'm wondering if this kind of helper script could be extended to
> >> have that "look around it" thing to help.
> >
> > I think that issue is solved by addr2line's '--inline' option, which the
> > script uses:
>
> Another small gotcha is that stack trace addresses are _return
> addresses_, not callsites. So you'll sometimes want to pass 'addr - 1'
> instead of just addr, as the next address (the return address) may
> belong to a completely unrelated deeply inlined function.
Hm, good point. In that case, should it *always* subtract 1? (Except
when the offset is already 0, of course.)
--
Josh
next prev parent reply other threads:[~2016-09-17 18:54 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
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 [this message]
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=20160917185413.mms2zb3lkmrk6wy5@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=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®