On Wed, Oct 13, 2010 at 10:45:18PM +0100, Ed W wrote: > I traced the workaround to either disabling PAX_MPROTECT in the host > kernel, or calling "paxctl -m" on the test binary (was expecting to need > it on the library instead?) > > Can anyone shed some light on why creating a pthread (old linux threads) > on 0.9.30.1 / 0.9.31 should be tickling mprotect?
Are you perfectly sure you're using the *old* LinuxThreads ? A quick look only revealed calls to mprotect() in the "new" implementation. -- Richard Braun _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
