From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28148] eu-addr2line reports function name of the caller when code is inlined
Date: Thu, 02 Nov 2023 13:30:02 +0000 [thread overview]
Message-ID: <bug-28148-10460-c3O15nZwzo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28148-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28148
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #1)
> Is this still an issue?
>
> With binutils addr2line 2.39 I get:
>
> $ addr2line -f -e inlined-bug.elf 20400e10
> irq_disable
> /home/john/src/RIOT/cpu/riscv_common/include/irq_arch.h:62
>
> And with eu-addr2line 0.189:
>
> $ eu-addr2line -f -e inlined-bug.elf 20400e10
> irq_disable inlined at /home/john/src/RIOT/core/atomic_c11.c:212:1 in
> __atomic_fetch_and_4
> /home/john/src/RIOT/cpu/riscv_common/include/irq_arch.h:62:5
>
> $ eu-addr2line -a --pretty-print -i -f -e inlined-bug.elf 20400e10
> 0x20400e10: irq_disable at
> /home/john/src/RIOT/cpu/riscv_common/include/irq_arch.h:62:5
> (inlined by) __atomic_fetch_and_4 at
> /home/john/src/RIOT/core/atomic_c11.c:212:1
Assuming this is now fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-11-02 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 12:30 [Bug libdw/28148] New: " n2knqf5ogu at bsogq dot anonbox.net
2023-10-06 11:29 ` [Bug libdw/28148] " mark at klomp dot org
2023-11-02 13:30 ` mark at klomp dot org [this message]
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-28148-10460-c3O15nZwzo@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).