From: Ulrich Drepper <drepper@gmail.com>
To: libc-hacker@sourceware.org
Subject: relative relocation handling
Date: Sun, 16 Oct 2011 14:27:00 -0000 [thread overview]
Message-ID: <CAOPLpQch-Kiqo-q7zmwnzVEh9s+7KJvh4+KEWSx-R_ar0Q8UJg@mail.gmail.com> (raw)
I just checked in a patch which fixes a problem with the relative
relocation handling. I don't think anyone ever hit it, otherwise it
would have been noticed. ld.so skipped over the number of relocations
indicated in DT_RELCOUNT etc even for sections other than
DT_REL/DT_RELA.
reply other threads:[~2011-10-16 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOPLpQch-Kiqo-q7zmwnzVEh9s+7KJvh4+KEWSx-R_ar0Q8UJg@mail.gmail.com \
--to=drepper@gmail.com \
--cc=libc-hacker@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).