From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/30980] offline.c:53: dwfl_offline_section_address: Assertion `mod->e_type == ET_REL' failed.
Date: Wed, 18 Oct 2023 14:01:48 +0000 [thread overview]
Message-ID: <bug-30980-10460-qDsF4w2ims@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30980-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30980
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
This however is really odd and might explain why we get onto an ET_REL path:
$ eu-readelf -x .gnu_debuglink
~/Downloads/libjavascriptcoregtk-4.1.so.0.4.10.zst
Hex dump of section [28] '.gnu_debuglink', 84 bytes at offset 0x1fbedc8:
0x00000000 63727469 2e6f2e64 65627567 00000000 crti.o.debug....
0x00000010 2aa4dad4 63727462 6567696e 532e6f2e *...crtbeginS.o.
0x00000020 64656275 67000000 39c05e5d 63727465 debug...9.^]crte
0x00000030 6e64532e 6f2e6465 62756700 6b271cc4 ndS.o.debug.k'..
0x00000040 6372746e 2e6f2e64 65627567 00000000 crtn.o.debug....
0x00000050 5fbdc21b _...
So when looking for the separate .debug file, when we don't have a build-id
match, we will search for crti.o.debug...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-18 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 13:44 [Bug libdw/30980] New: " cebtenzzre at gmail dot com
2023-10-18 13:57 ` [Bug libdw/30980] " mark at klomp dot org
2023-10-18 14:01 ` mark at klomp dot org [this message]
2023-10-18 14:19 ` mark at klomp dot org
2023-10-18 14:26 ` mark at klomp dot org
2023-10-25 3:21 ` sam at gentoo dot org
2023-11-01 23:36 ` amerey at redhat dot com
2023-11-02 12:17 ` mark at klomp dot org
2023-11-02 13:44 ` amerey at redhat dot com
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-30980-10460-qDsF4w2ims@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).