[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzFUuCniKCutTVNchuhY-bkB=3JkPv46rYwpx1Q0_5n0w@mail.gmail.com>
Date: Mon, 13 Nov 2017 12:56:31 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Fengguang Wu <fengguang.wu@...el.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Network Development <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
intel-wired-lan@...ts.osuosl.org, Michal Marek <mmarek@...e.cz>,
Sam Ravnborg <sam@...nborg.org>,
Dirk Gouders <dirk@...ders.net>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
kbuild test robot <lkp@...el.com>,
"Zhang, Rui" <rui.zhang@...el.com>,
"Lu, Aaron" <aaron.lu@...el.com>, "H.J. Lu" <hjl.tools@...il.com>
Subject: Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line
On Mon, Nov 13, 2017 at 12:10 PM, Andi Kleen <ak@...ux.intel.com> wrote:
>
> You're right. It works for line information, but strangely not for
> inlines. I assume it can be fixed.
So I'm not 100% sure it's strictly a addr2line bug.
We do more than just link the vmlinux file. There's that whole
complicated script for our final link in
scripts/link-vmlinux.sh
which links in all the kallsyms information etc, but also does things
like the exception table sorting.
So it's possible that addr2line works fine on a normal executable, but
that we've done some munging that then makes it not really do the
right thing for vmlinux.
But it is also equally possible that addr2line simply doesn't
understand -gsplit-dwarf at all. I've never seen it used outside the
kernel.
Linus
Powered by blists - more mailing lists