public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifix.com>
To: David Arnold <david@mantara.com>
Cc: binutils@sourceware.org
Subject: Re: Use of readelf -D option
Date: Sat, 21 Apr 2007 19:50:00 -0000	[thread overview]
Message-ID: <1177176212.2685.13.camel@localhost.localdomain> (raw)
In-Reply-To: <15088.1176594167@d.0x1.org>

On Sun, 2007-04-15 at 09:42 +1000, David Arnold wrote:
> am i correct in remembering that on x86_64 and with recent binutils,
> there's only a DT_GNU_HASH?

I don't believe it is the default in the FSF tree.  I see DT_HASH when I
try it on my x86_64 machine.  Perhaps Red Hat applied a patch to change
the default?

There is a linker option --hash-type= that you can use to change this.
Option values are sysv, gnu, or both.  So this might work as a short
term workaround.

> it looks like i will need to gather some more information, but possibly
> the check that the .dynamic contains a DT_HASH should also accept a
> DT_GNU_HASH?

It is a little more complicated than that.  readelf is using the DT_HASH
info to compute the list of symbols.  So we need equivalent code that
works for DT_GNU_HASH.

I'd suggest filing a bug report as HJ already mentioned.  If you want
RHEL fixed, you will have to file a bug report with Red Hat.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com


      parent reply	other threads:[~2007-04-21 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11  1:11 David Arnold
2007-04-14  1:27 ` Jim Wilson
2007-04-15  4:59   ` David Arnold
2007-04-15  7:48     ` H. J. Lu
2007-04-21 19:50     ` Jim Wilson [this message]

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=1177176212.2685.13.camel@localhost.localdomain \
    --to=wilson@specifix.com \
    --cc=binutils@sourceware.org \
    --cc=david@mantara.com \
    /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).