To elaborate on my previous post: There seems to be some problem with TLS (Thread-local storage, __thread keyword). This workaround just replaces TLS with a locking mechanism, but this doesn't fix the original problem - no idea where that problem originates.
(libselinux_2.0.65-2 on Intrepid, gcc 4.3.2 [4.3.2-1ubuntu11]) -- SETRANS + libavg = SIGSEGV on Hardy https://bugs.launchpad.net/bugs/237156 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
