From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/26599] New: eu-readelf -n works on /boot/vmlinuz-* but debuginfod-find doesn't
Date: Fri, 11 Sep 2020 10:12:03 +0000 [thread overview]
Message-ID: <bug-26599-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26599
Bug ID: 26599
Summary: eu-readelf -n works on /boot/vmlinuz-* but
debuginfod-find doesn't
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
eu-readelf appears to unwrap the bzImage header on a vmlinuz kernel file, and
can thus extract buildids, but debuginfod-find cannot:
% eu-readelf -n /lib/modules/5.7.15-200.fc32.x86_64/vmlinuz
[...]
GNU 20 GNU_BUILD_ID
Build ID: 8820b044b7717b53bd9a9795a1fbca152d2fae63
% debuginfod-find debuginfo /lib/modules/5.7.15-200.fc32.x86_64/vmlinuz
Cannot extract build-id from /lib/modules/5.7.15-200.fc32.x86_64/vmlinuz:
invalid `Elf' handle
It would be handy to teach debuginfod-find how to use the elfutils entry point
that unwraps bzImage.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-09-11 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 10:12 fche at redhat dot com [this message]
2020-09-11 10:39 ` [Bug debuginfod/26599] " mark at klomp dot org
2020-09-15 13:46 ` 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-26599-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).