public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-bz at firstfloor dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12939] New: resolving shared library symbols returns wrong file
Date: Mon, 27 Jun 2011 16:52:00 -0000 [thread overview]
Message-ID: <bug-12939-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=12939
Summary: resolving shared library symbols returns wrong file
Product: glibc
Version: 2.14
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: andi-bz@firstfloor.org
dladdr() when called with a shared library symbol like printf
returns the name of the main executable in dli_fname
I suspect it happens because it resolves the PLT, but that's clearly
unexpected and makes it hard to use if you want to know
what .so printf is in. Is there a way around it?
Maybe the function could check for PLTs and resolve them?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-06-27 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:52 andi-bz at firstfloor dot org [this message]
2012-02-21 2:15 ` [Bug ld.so|libdl/12939] " jsm28 at gcc dot gnu.org
2012-12-19 10:47 ` [Bug dynamic-link/12939] " schwab@linux-m68k.org
2014-06-27 13:03 ` fweimer at redhat dot com
2014-07-02 15:38 ` alexander.long91 at gmail dot com
2014-07-02 15:39 ` alexander.long91 at gmail dot com
2015-01-12 20:27 ` p.kopyl at samsung dot com
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=bug-12939-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.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).