public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: RTLD_DEEPBIND
Date: Thu, 23 Sep 2004 07:48:00 -0000	[thread overview]
Message-ID: <41527FC6.9050903@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just committed a set of patches implementing an often requested
feature.  If dlopen is used with this flag, the objects thusly loaded
get a lookup scope which has the scope of the loader before the global
scope.  I.e., if the objects are self-contained they will not use the
global scope.  This can be used to work around problems of morons who
cannot keep ABIs stable and have the same symbol name in different DSOs.

Only lightly tested (see the new tests) but I think the code is OK.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBUn/G2ijCOnn/RHQRAoZxAJwM7hX8DNhZKcC7INRx+uv/JGoOYQCgmzuL
99EvoRp9mFfTq6mAH04Mc4k=
=JCQf
-----END PGP SIGNATURE-----

                 reply	other threads:[~2004-09-23  7:48 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=41527FC6.9050903@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@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).