From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24344] New: [dwz] Support relocatable elf
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24344-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24344
Bug ID: 24344
Summary: [dwz] Support relocatable elf
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
When building openSUSE:Factory/kernel-vanilla I get lots of "is not a shared
library" errors, like f.i.:
...
[ 3916s] dwz:
"./lib/modules/4.20.13-0-vanilla/kernel/sound/usb/6fire/snd-usb-6fire.ko.debug"
is not a shared library
...
This is a file with debug info for a loadable module, which is an ELF
relocatable:
...
$ file
./usr/lib/debug/lib/modules/4.20.13-0-vanilla/kernel/sound/usb/6fire/snd-usb-6fire.ko.debug
./usr/lib/debug/lib/modules/4.20.13-0-vanilla/kernel/sound/usb/6fire/snd-usb-6fire.ko.debug:
ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV),
BuildID[sha1]=5f01e04c17fe8b2f9941b0981ff89ebbe3eb308e, with debug_info, not
stripped
...
Dwz doesn't support relocatables atm. To do so, it would have to add support to
parse and update RELA section related to debug sections.
Not sure if this feature would be useful for anything else than loadable
modules.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-14 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` [Bug default/24344] " vries at gcc dot gnu.org
2020-09-13 14:03 ` mark at klomp dot org
2020-09-13 14:50 ` mark at klomp dot org
2024-02-05 12:04 ` [Bug default/24344] [dwz] Support relocatable elf (linux kernel modules) 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-24344-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).