Stuart Henderson <s...@spacehopper.org> wrote: > +allow dlopen() to search for libc rather than parsing ldconfig -r to > +decide on a version number. > + > +(would this make sense for all libraries? I'm not sure exactly what > +parameters this might be called with, whether it's just a bare name or > +could have a path/version in it).
I wonder how many places we have the same problem with other libraries. libc.so is just being strict and failing hard. Other libraries may fail in extremely subtle ways. One caller changes global state in libfoo.so.A.A's mapping, another caller uses libfoo.so.X.X's mapping without having the initialized state. Why would we ever want two libfoo.so.?.? mapped into memory? I suspect the hard-to-diagnose bugs are more dangerous than the capability to do so.
