[Bug dynamic-link/19884] Discrepancy between documented and actual search path for shared libraries

["njs at pobox dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19884

--- Comment #2 from Nathaniel J. Smith <njs at pobox dot com> ---
*If* the same library is loaded twice, then having the two copies share state
makes perfect sense. The problem here is that according to all the library
lookup rules, we're actually loading two different libraries that live in two
different files at two different locations, yet they still end up sharing
state...

Yes, the two different libraries have the same SONAME, but there's no guarantee
that all libraries with a given SONAME will be interchangeable.
"interchangeable" means fully backwards *and* forward compatible, and that's
not even true for basic libraries like glibc or libgcc.

(Actually, I'm not even sure how much state the two copies share -- since
they're in different scopes they get different relocation processing, right? I
guess those are in a different segment or something, so the two copies share
.data but not relocations or something?)

-- 
You are receiving this mail because:
You are on the CC list for the bug.