* [Bug tools/29282] New: eu-addr2line -k doesn't display correct file:line in arm.
@ 2022-06-24 0:16 panxh_ran at 163 dot com
2022-06-24 1:12 ` [Bug tools/29282] " fche at redhat dot com
2023-10-05 15:29 ` mark at klomp dot org
0 siblings, 2 replies; 3+ messages in thread
From: panxh_ran at 163 dot com @ 2022-06-24 0:16 UTC (permalink / raw)
To: elfutils-devel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug tools/29282] eu-addr2line -k doesn't display correct file:line in arm.
2022-06-24 0:16 [Bug tools/29282] New: eu-addr2line -k doesn't display correct file:line in arm panxh_ran at 163 dot com
@ 2022-06-24 1:12 ` fche at redhat dot com
2023-10-05 15:29 ` mark at klomp dot org
1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2022-06-24 1:12 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=29282
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
possibly another side-effect of this upstream gcc bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2092438
and not an elfutils bug per se
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug tools/29282] eu-addr2line -k doesn't display correct file:line in arm.
2022-06-24 0:16 [Bug tools/29282] New: eu-addr2line -k doesn't display correct file:line in arm panxh_ran at 163 dot com
2022-06-24 1:12 ` [Bug tools/29282] " fche at redhat dot com
@ 2023-10-05 15:29 ` mark at klomp dot org
1 sibling, 0 replies; 3+ messages in thread
From: mark at klomp dot org @ 2023-10-05 15:29 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=29282
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=103525
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Which seems to be the following gcc bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103525
panxiaohe is your kernel build with CONFIG_DYNAMIC_FTRACE=y ? which uses
-fpatchable-function-entry ?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-05 15:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-24 0:16 [Bug tools/29282] New: eu-addr2line -k doesn't display correct file:line in arm panxh_ran at 163 dot com
2022-06-24 1:12 ` [Bug tools/29282] " fche at redhat dot com
2023-10-05 15:29 ` mark at klomp dot org
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).