From: "vt at altlinux dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27029] New: eu-strip: bad relocation after dwz vmlinux
Date: Mon, 07 Dec 2020 15:17:03 +0000 [thread overview]
Message-ID: <bug-27029-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27029
Bug ID: 27029
Summary: eu-strip: bad relocation after dwz vmlinux
Product: dwz
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vt at altlinux dot org
CC: dwz at sourceware dot org
Target Milestone: ---
I don't know if it's sane or not to run dwz on vmlinux, but after dwz run
eu-strip produces error message:
$ cp
/usr/lib/debug/usr/lib/debug/lib/modules/4.19.160-rt-alt1.rt69/vmlinux.debug
vmlinux.debug
$ dwz vmlinux.debug
$ eu-strip --reloc-debug-sections-only vmlinux.debug
eu-strip: bad relocation
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-07 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 15:17 vt at altlinux dot org [this message]
2020-12-07 15:19 ` [Bug default/27029] " vries at gcc dot gnu.org
2021-02-12 14:31 ` 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-27029-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).