[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171113214148.GP8522@tassilo.jf.intel.com>
Date: Mon, 13 Nov 2017 13:41:48 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
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:56:31PM -0800, Linus Torvalds wrote:
> 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.
It seems to be broken for normal programs too
$ cat tinline.c
int i;
static inline int finline(void)
{
i++;
}
main()
{
finline();
}
$ gcc -O2 -gsplit-dwarf tinline.c
$ addr2line -i -e a.out 0x4003b0
/home/ak/tsrc/tinline.c:6
$ gcc -O2 -g tinline.c
$ addr2line -i -e a.out 0x4003b0
/home/ak/tsrc/tinline.c:6
/home/ak/tsrc/tinline.c:12
$
I filed https://sourceware.org/bugzilla/show_bug.cgi?id=22434
-Andi
Powered by blists - more mailing lists