This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Expected semantics of versioned symbol resolution


Florian Weimer <fweimer@redhat.com> writes:

> The current ld.so behavior seems far from uniform.  Existing binaries
> reference pthread_mutex_lock, version GLIBC_2.2.5, soname libc.so.6. Yet
> we clearly expect that these are bound to the pthread_mutex_lock in
> libpthread.so.0, not the one in libc.so.6, once libpthread is loaded
> (irrespective of the link order).

Do they?  Note that the functions defined in nptl/forward.c forward the
calls to libpthread once the latter is loaded, but are no-ops otherwise.
The binding doesn't change from what was recorded during linking.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]