70ba1e8fc1
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. |
||
|---|---|---|
| .. | ||
| arch | ||
| support | ||
| sys | ||
| thread | ||
| libthr.3 | ||
| Makefile | ||
| pthread.map | ||