From: leslie.polzer@gmx.net
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: unable to link to a static library present alongside a shared library
Date: Thu, 19 Apr 2007 14:34:36 +0200 [thread overview]
Message-ID: <20070419123436.GA19433@wintermute.farpoint> (raw)
In-Reply-To: <46273FFC.2070902@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Thu, Apr 19, 2007 at 03:40:04PM +0530, Shriramana Sharma wrote:
> >meant to be loaded. OTOH, the Linux loader doesn't care where a
> >symbol comes from, so long as something defines it.
>
> And what would be the implications of that? I mean, what happens
> practically because of that?
You can deceive the program by using LD_PRELOAD tricks:
You may trace a certain group of functions,
chosen by you.
You may customize applications without having access to their
source or modify them in other ways as you see fit (as long as
it's dependent on a dynamically bound library function).
And so on.
Leslie
--
NEW homepage: https://viridian.dnsalias.net/~sky/homepage/
gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-19 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 12:09 unable to link to a static library present alongside a shared library Shriramana Sharma
2007-04-18 12:19 ` cyon.john
2007-04-18 12:33 ` Shriramana Sharma
2007-04-18 14:00 ` cyon.john
2007-04-18 17:34 ` Shriramana Sharma
2007-04-18 15:12 ` Glynn Clements
2007-04-18 18:40 ` Shriramana Sharma
2007-04-18 20:18 ` Glynn Clements
2007-04-19 10:10 ` Shriramana Sharma
2007-04-19 12:34 ` leslie.polzer [this message]
2007-04-19 13:48 ` Shriramana Sharma
2007-04-19 16:30 ` leslie.polzer
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=20070419123436.GA19433@wintermute.farpoint \
--to=leslie.polzer@gmx.net \
--cc=linux-c-programming@vger.kernel.org \
--cc=samjnaa@gmail.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 NNTP newsgroup(s).