public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "panxh_ran at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/29282] New: eu-addr2line -k doesn't display correct file:line in arm.
Date: Fri, 24 Jun 2022 00:16:49 +0000	[thread overview]
Message-ID: <bug-29282-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29282

            Bug ID: 29282
           Summary: eu-addr2line -k doesn't display correct file:line in
                    arm.
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tools
          Assignee: unassigned at sourceware dot org
          Reporter: panxh_ran at 163 dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Hello, when using eu-addr2line -k to get line infomation of kernel symbols, it
often displays wrong file:line in arm.
Steps:
1.Get func address from /proc/kallsyms.
2.Use eu-addr2line -k <address> to get file name and line number.
Compare the line number with source file,and we find the line number is wrong.

It seems that the following kernel commit that adds NOPs at function entry
causes the problem.
Elfutils needs to adapt this feature.
> Fixes: 3b23e4991fb6 ("arm64: implement ftrace with regs")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-06-24  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  0:16 panxh_ran at 163 dot com [this message]
2022-06-24  1:12 ` [Bug tools/29282] " fche at redhat dot com
2023-10-05 15:29 ` mark at klomp dot org

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=bug-29282-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).