Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line
Date: Mon, 13 Nov 2017 13:41:48 -0800	[thread overview]
Message-ID: <20171113214148.GP8522@tassilo.jf.intel.com> (raw)
In-Reply-To: <CA+55aFzFUuCniKCutTVNchuhY-bkB=3JkPv46rYwpx1Q0_5n0w@mail.gmail.com>

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@linux.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


  reply	other threads:[~2017-11-13 21:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171107102156.3fgxt6y6v5y2kqnf@wfg-t540p.sh.intel.com>
     [not found] ` <CA+55aFwqxZiN_XrZqvbtCsc8W=w895RaB1sjuVP1aTj8JStxzg@mail.gmail.com>
     [not found]   ` <20171108094832.qxvkawpw2snpcbvh@wfg-t540p.sh.intel.com>
2017-11-08 16:20     ` [Intel-wired-lan] [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf 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           ` [Intel-wired-lan] 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 [this message]
2017-11-13 21:57                       ` Linus Torvalds
2017-11-13 23:51                         ` Andi Kleen
2017-11-14  8:13               ` 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=20171113214148.GP8522@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=intel-wired-lan@osuosl.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