From: "slyfox at inbox dot ru" <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: Sat, 24 Nov 2018 00:54:00 -0000 [thread overview]
Message-ID: <bug-23916-10460-5KjceyHKhJ@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 #1 from Sergei Trofimovich <slyfox at inbox dot ru> ---
objtool is a part of linux kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/objtool
Attached b.tar.gz contains:
- objtool binary
- object files before and after mangling with objtool
Note the .debug_info offset and alignment change:
$ readelf -a rapl.o.back > pre
$ readelf -a rapl.o > post
$ diff -U 0 pre post
- [ 4] .debug_info PROGBITS 0000000000000000 00000047
- 000000000000003c 0000000000000000 C 0 0 1
+ [ 4] .debug_info PROGBITS 0000000000000000 00000048
+ 000000000000003c 0000000000000000 C 0 0 8
My wild guess is that section's start is not adjusted correctly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-11-24 0:54 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 ` slyfox at inbox dot ru [this message]
2018-11-24 1:04 ` [Bug libelf/23916] " 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
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-5KjceyHKhJ@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).