From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/28928] Wrong dynamic section entry number
Date: Fri, 15 Apr 2022 15:22:45 +0000 [thread overview]
Message-ID: <bug-28928-10460-kvU1xO5tsC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28928-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28928
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #14042|0 |1
is obsolete| |
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Created attachment 14064
--> https://sourceware.org/bugzilla/attachment.cgi?id=14064&action=edit
readelf: Don't consider padding DT_NULL as dynamic section
Good find. And binutils readelf does get this right.
I see you made this block PR28873. And you are right that we should first get
this correct before doing the the -D dance going through the dynamic segment
showing information.
But for -d we don't have to go through the phdrs and the dynamic segment, we
can just use the section data directly.
I made that adjustment and added some ChangeLog entries.
See attached and at:
https://code.wildebeest.org/git/user/mjw/elfutils/commit/?h=pr14042
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-15 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:15 [Bug tools/28928] New: " dichen at redhat dot com
2022-02-28 13:19 ` [Bug tools/28928] " dichen at redhat dot com
2022-03-30 11:42 ` dichen at redhat dot com
2022-03-30 11:48 ` dichen at redhat dot com
2022-04-15 15:22 ` mark at klomp dot org [this message]
2022-04-15 15:46 ` dichen at redhat dot com
2022-04-19 8:18 ` 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-28928-10460-kvU1xO5tsC@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).