[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMe9rOoeV-Y3gYAEpPXOQuRxxNq2GP-Zwm0Q+sohRduRyXUv7g@mail.gmail.com>
Date: Mon, 13 Nov 2017 12:14:11 -0800
From: "H.J. Lu" <hjl.tools@...il.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
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>
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:
>> Put another way: the CONFIG_DEBUG_INFO_SPLIT option is useless. Yes,
>> it saves time and disk space, but does so at the expense of making all
>> the debug information unavailable to basic tools.
>
> You're right. It works for line information, but strangely not for
> inlines. I assume it can be fixed.
>
Is there a binutils bug report for this?
--
H.J.
Powered by blists - more mailing lists