public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Cc: Anibal Monsalve Salazar <Anibal.MonsalveSalazar@imgtec.com>
Subject: [RFD] How legal is it to delete dynamic tags?
Date: Fri, 15 Apr 2016 15:08:00 -0000	[thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023537E3D685D@hhmail02.hh.imgtec.org> (raw)

I have a bug report from Debian showing that the DT_MIPS_RLD_MAP_REL
tag (introduced on MIPS to support shared library debug with PIE)
can be corrupted by a program called chrpath.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818909#43

chrpath is designed to alter or remove DT_RPATH entries. Removal is
a problem when such an entry precedes DT_MIPS_RLD_MAP_REL as the
relative offset stored in DT_MIPS_RLD_MAP_REL then points to the
wrong address.

Firstly, to what extent is it OK to just delete a dynamic tag rather
than set it to DT_NULL?

Secondly was it a bad decision to create a slot-relative dynamic
tag? I.e. If I were to fix chrpath to know that DT_MIPS_RLD_MAP_REL
needs updating... are there likely to be more utilities out there
that fiddle with dynamic tags in this way?

Thanks for any insight you can offer.

Matthew

             reply	other threads:[~2016-04-15 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 15:08 Matthew Fortune [this message]
2016-04-15 22:25 ` Alan Modra
2016-04-18  9:44   ` Matthew Fortune
2016-04-15 23:13 ` Nathaniel Smith
2016-04-15 23:17   ` Nathaniel Smith
2016-04-18  9:45     ` Matthew Fortune

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=6D39441BF12EF246A7ABCE6654B023537E3D685D@hhmail02.hh.imgtec.org \
    --to=matthew.fortune@imgtec.com \
    --cc=Anibal.MonsalveSalazar@imgtec.com \
    --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).