Ryan Stone aad93b043a r179417 introduced a bug into pthread_once(). Previously pthread_once()
used a global pthread_mutex_t for synchronization.  r179417 replaced that
with an implementation that directly used atomic instructions and thr_*
syscalls to synchronize callers to pthread_once.  However, calling
pthread_mutex_lock on the global mutex implicitly ensured that
_thr_check_init() had been called but with r179417 this was no longer
guaranteed.  This meant that if you were unlucky enough to have your first
call into libthr be a call to pthread_once(), you would segfault when
trying to access the pointer returned by _get_curthread().

The fix is to explicitly call _thr_check_init() from pthread_once().

Reviewed by:	davidxu
Approved by:	emaste (mentor)
MFC after:	1 week
2011-04-20 14:19:34 +00:00
..
2010-05-24 13:44:39 +00:00
2010-09-30 12:59:56 +00:00
2010-12-22 05:01:52 +00:00
2010-09-19 08:55:36 +00:00
2010-12-22 05:01:52 +00:00
2010-12-22 05:01:52 +00:00
2011-01-06 08:13:30 +00:00
2011-01-11 01:57:02 +00:00
2010-12-22 05:03:24 +00:00
2010-12-22 05:01:52 +00:00
2010-12-22 05:01:52 +00:00