Subject: Runtime loading of libpthread
To: None <email@example.com>
From: Ceri Storey <firstname.lastname@example.org>
Date: 12/21/2003 19:38:44
I don't suppose there's been any advancement on this subject, that is,
that runtime loading of libpthread into a non-threaded application
causes functions which rely on the libc thread-stubs (eg: malloc) to
I'd have expected that the new strongly aliased thread_stubs from
libpthread would be used to override the weakly aliased ones from libc.
However, this doesn't seem to be being done.
Is this to avoid fun problems such as one function which expects the
data to be laid out one way to be called with data laid out another way?
(Eg: like when you find you've got two differing versions of a library
loaded into a process). Or is it just technically infeasible?
Ceri Storey <email@example.com>