From: "n2knqf5ogu at bsogq dot anonbox.net" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/27805] New: libdwfl: Unable to extract source line information for RISC-V binary
Date: Fri, 30 Apr 2021 12:31:12 +0000 [thread overview]
Message-ID: <bug-27805-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27805
Bug ID: 27805
Summary: libdwfl: Unable to extract source line information for
RISC-V binary
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libdw
Assignee: unassigned at sourceware dot org
Reporter: n2knqf5ogu at bsogq dot anonbox.net
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 13416
--> https://sourceware.org/bugzilla/attachment.cgi?id=13416&action=edit
RV32IMC binary to reproduce the outlined issue
For the attached RV32IMC (i.e. RISC-V) binary, libdwfl from elfutlis 0.183 is
incapable of extracting source line information from provided DWARF debugging
information. This can be easily reproduced by comparing the behavior of
elfutils's addr2line with binutils's addr2line program.
With binutils:
$ addr2line --version
GNU addr2line (GNU Binutils) 2.35.2
$ addr2line -e /tmp/elfutils-srcline-bug.elf 20400058
/home/john/src/RIOT/examples/hello-world/main.c:26
With elfutils:
$ addr2line --version
addr2line (elfutils) 0.183
$ addr2line -e /tmp/elfutils-srcline-bug.elf 20400058
??:0
Briefly debugging this, it seems to me that dwfl_module_getsrc seems to return
NULL and error out with DWARF_E_INVALID_OFFSET for this given binary.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-30 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 12:31 n2knqf5ogu at bsogq dot anonbox.net [this message]
2021-05-01 20:48 ` [Bug libdw/27805] " wilson at gcc dot gnu.org
2021-05-05 14:36 ` mark at klomp dot org
2021-05-05 15:42 ` wilson at gcc dot gnu.org
2021-05-05 15:59 ` wilson at gcc dot gnu.org
2021-05-06 9:43 ` mark at klomp dot org
2021-07-28 11:55 ` n2knqf5ogu at bsogq dot anonbox.net
2023-10-06 12:10 ` mark at klomp dot org
2023-10-09 16:15 ` 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-27805-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).