From: Jakub Jelinek <jakub@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Manuel Arriaga <manuelarriaga1980@gmail.com>, binutils@sourceware.org
Subject: Re: identifying symbol versions available to dlvsym
Date: Fri, 21 Dec 2007 16:27:00 -0000 [thread overview]
Message-ID: <20071221163326.GH2947@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <476BE851.6040705@redhat.com>
On Fri, Dec 21, 2007 at 04:22:41PM +0000, Nick Clifton wrote:
> I am sorry that it has taken so long for us to reply to your posts.
>
> >OK, so some experimentation and additional searching showed me that
> >GNU libc's fopen does not necessarily reside on /lib/libc.so.6. By
> >looking into a different shared lib, one reads
> >
> >$ readelf -s /lib64/libc.so.6 |grep " fopen@"
> > 162: 000000000005f4c0 10 FUNC GLOBAL DEFAULT 12
> > fopen@@GLIBC_2.2.5
> >
> >which is precisely the version number that works with dlvsym().
> >
> >How could I have found this programatically? To identify the version
> >of fopen being used, can I do better than
> >
> >1) running ldd on an executable containing a call to fopen();
> >2) run readelf -s | grep fopen on each of the libs listed; and
> >3) using the first version string I find in 2) in my calls to dlvsym?
Well, usually you don't want the first version, but the default version (the
one with @@ instead of just @), because that matches the headers of the
library and what you'd normally get if you directly linked against the
library rather than using dlvsym.
Jakub
next prev parent reply other threads:[~2007-12-21 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 17:48 Manuel Arriaga
2007-12-03 18:14 ` Manuel Arriaga
2007-12-21 16:23 ` Nick Clifton
2007-12-21 16:27 ` Jakub Jelinek [this message]
2007-12-22 17:09 ` Manuel Arriaga
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=20071221163326.GH2947@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=binutils@sourceware.org \
--cc=manuelarriaga1980@gmail.com \
--cc=nickc@redhat.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).