From: Fengguang Wu <fengguang.wu@intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
intel-wired-lan@lists.osuosl.org, Michal Marek <mmarek@suse.cz>,
Sam Ravnborg <sam@ravnborg.org>, Dirk Gouders <dirk@gouders.net>,
linux-kbuild@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>,
"Lu, Aaron" <aaron.lu@intel.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line
Date: Tue, 14 Nov 2017 16:13:36 +0800 [thread overview]
Message-ID: <20171114081336.e32bqhcu3eu4yl23@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20171113185227.GM8522@tassilo.jf.intel.com>
Hi Andi,
On Mon, Nov 13, 2017 at 10:52:27AM -0800, Andi Kleen wrote:
>> > It's the "CONFIG_DEBUG_INFO_SPLIT" thing that makes faddr2line unable
>> > to see the inlining information,
>> >
>> > Using OPTIMIZE_INLINING is fine.
>>
>> Good to know that!
>
>It works for me. Perhaps your binutils is too old? It was
>added at some point. Can you try upgrading?
>
>% ./linux/scripts/faddr2line obj/vmlinux schedule+10
>schedule+10/0x80:
>schedule at arch/x86/include/asm/current.h:15
>
>% addr2line --version
>GNU addr2line version 2.27-24.fc26
I use debian and tried addr2line in 2 systems:
GNU addr2line (GNU Binutils for Debian) 2.28
GNU addr2line (GNU Binutils for Debian) 2.29.1
Regards,
Fengguang
next prev parent reply other threads:[~2017-11-14 8:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 10:21 [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu
2017-11-07 16:25 ` Linus Torvalds
2017-11-07 16:46 ` Fengguang Wu
2017-11-08 9:48 ` Fengguang Wu
2017-11-08 16:20 ` Linus Torvalds
2017-11-08 17:12 ` Fengguang Wu
2017-11-08 17:18 ` Fengguang Wu
2017-11-08 18:05 ` Linus Torvalds
2017-11-08 18:36 ` Alexander Duyck
2017-11-09 3:12 ` Fengguang Wu
2017-11-09 4:09 ` Fengguang Wu
2017-11-09 7:22 ` Fengguang Wu
2017-11-09 6:34 ` Cong Wang
2017-11-09 6:55 ` Fengguang Wu
2017-11-09 7:43 ` Fengguang Wu
2017-11-09 15:51 ` Girish Moodalbail
2017-11-10 0:16 ` Cong Wang
2017-11-12 19:31 ` Linus Torvalds
2017-11-13 1:13 ` CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line Fengguang Wu
2017-11-13 2:05 ` Zhang Rui
2017-11-13 2:22 ` Fengguang Wu
2017-11-13 18:52 ` Andi Kleen
2017-11-13 19:14 ` Linus Torvalds
2017-11-13 20:10 ` Andi Kleen
2017-11-13 20:14 ` H.J. Lu
2017-11-13 20:56 ` Linus Torvalds
2017-11-13 21:41 ` Andi Kleen
2017-11-13 21:57 ` Linus Torvalds
2017-11-13 23:51 ` Andi Kleen
2017-11-14 8:13 ` Fengguang Wu [this message]
2017-11-09 2:43 ` [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu
2017-11-09 6:48 ` Fengguang Wu
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=20171114081336.e32bqhcu3eu4yl23@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=aaron.lu@intel.com \
--cc=ak@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dirk@gouders.net \
--cc=hjl.tools@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).