From: "Thomas Röthenbacher" <thomas@43t.de>
To: binutils@sourceware.org
Subject: bfd enforces a specific value of sh_info on SHT_GNU_verneed
Date: Fri, 13 May 2022 21:17:32 +0200 [thread overview]
Message-ID: <716eb868d262e063382c7b63901fb02dfad9f2bb.camel@mailbox.org> (raw)
Hello,
as stated in the subect, bfd (and therefore `objdump -d`) seems to fail
in _bfd_elf_slurp_version_tables if the value of sh_info for a
".gnu.version_r" section (SHT_GNU_verdef) is zero.
I couldn't however find a specification to justify this behaviour or
anything specifying the sh_info field of this section type at all.
The only reference I could find, was in the SUN "Linker and Libraries
Guide", where they defined the sh_info value for their section type
SHT_SUNW_verdef. But does this standard apply here?
I'm asking, because a program I work with generates binaries that
violate this constraint, but can't really justify why it should NOT
just have a sh_info of zero in this section.
Thanks in advance for your replies,
Thomas
next reply other threads:[~2022-05-13 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 19:17 Thomas Röthenbacher [this message]
2022-05-14 1:06 ` Alan Modra
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=716eb868d262e063382c7b63901fb02dfad9f2bb.camel@mailbox.org \
--to=thomas@43t.de \
--cc=binutils@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).