From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/23916] [bisected] elifutils-0.175 broke kernel's objtool (elifutils-0.173 works)
Date: Mon, 26 Nov 2018 12:13:00 -0000 [thread overview]
Message-ID: <bug-23916-10460-mHjpMVKbah@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23916-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23916
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Sergei Trofimovich from comment #3)
> On a related note: should eu-elflint complain on originally compiled
> rapl.o.back (from tarball)? That would ease detecting non-conformant
> binutils versions.
Yes, that is probably a good idea, I filed two new bugs:
Bug 23920 - elflint should check sanity check Chdr fields and uncompressed data
of compressed sections
Bug 23921 - elflint should check (minimum) section alignment sanity
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-11-26 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 0:49 [Bug libelf/23916] New: " slyfox at inbox dot ru
2018-11-24 0:54 ` [Bug libelf/23916] " slyfox at inbox dot ru
2018-11-24 1:04 ` mark at klomp dot org
2018-11-24 10:31 ` slyfox at inbox dot ru
2018-11-24 22:09 ` mark at klomp dot org
2018-11-26 12:13 ` mark at klomp dot org [this message]
2018-11-26 12:16 ` mark at klomp dot org
2018-12-03 0:06 ` slyfox at inbox dot ru
2018-12-03 0:19 ` ldv at sourceware dot org
2018-12-05 11:55 ` 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-23916-10460-mHjpMVKbah@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).