On Wed, Mar 23, 2011 at 12:29 PM, Carmelo AMOROSO wrote: > indeed we have seen also some issue with dlopen, when TLS variables were > involved. One suspect we have is actually thread-safety. glibc use some > locking primitives to access TLS block, while we don't. > Not yet had a free time slot to look at this deeply.
i'm not sure how thread safety would play a role with TLS variables. TLS, by definition, is per-thread and that is guaranteed by the ABI/compiler/C lib/kernel down to the variable level, and that whole stack shouldnt be poking into any shared state (beyond shared .text). -mike _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
