peter b14c2e0572 When libthr and rtld start up, there are a number of magic spells cast ... in order to get the symbol binding state "just so". This is to allow locking to be activated and not run into recursion problems later. However, one of the magic bits involves an explicit call to _umtx_op() to force symbol resolution. It does a wakeup operation on a fake, uninitialized (ie: random contents) umtx. Since libthr isn't active, this is harmless. Nothing can match the random wakeup. However, valgrind finds this and is not amused. Normally I'd just write a suppression record for it, but the idea of passing random args to syscalls (on purpose) just doesn't feel right.		2008-12-07 02:32:49 +00:00
..
arch	Commit missing mips libthr support that I thought I'd committed earlier	2008-05-11 05:54:52 +00:00
support	Use thr_new syscall to create a new thread, obscure context operations	2005-04-23 02:48:59 +00:00
sys	__error could be called too early before libthr is initialized, test	2006-07-12 03:44:05 +00:00
thread	When libthr and rtld start up, there are a number of magic spells cast	2008-12-07 02:32:49 +00:00
libthr.3	- Stop calling libthr alternative as it's now the default	2007-10-22 10:13:38 +00:00
Makefile	Enable GCC stack protection (aka Propolice) for userland:	2008-06-25 21:33:28 +00:00
pthread.map	Make pthread_cleanup_push() and pthread_cleanup_pop() as a pair of macros,	2008-06-09 01:14:10 +00:00