Don't really spin on a spinlock; silently convert it to the same

low-level lock used by the libpthread implementation.  In the
future, we'll eliminate spinlocks from libc but that will wait
until after 5.1-release.

Don't call an application signal handler if the handler is
the same as the library-installed handler.  This seems to
be possible after a fork and is the cause of konsole hangs.

Approved by:	re@ (jhb)

1 files changed, 1 insertions, 0 deletions

diff --git a/lib/libpthread/thread/thr_init.c b/lib/libpthread/thread/thr_init.c
index 5bfb3c7..433f246 100644
--- a/lib/libpthread/thread/thr_init.c
+++ b/lib/libpthread/thread/thr_init.c
@@ -515,6 +515,7 @@ init_private(void)
 	if (_lock_init(&_keytable_lock, LCK_ADAPTIVE,
 	    _thr_lock_wait, _thr_lock_wakeup) != 0)
 		PANIC("Cannot initialize thread specific keytable lock");
+	_thr_spinlock_init();
 
 	/* Clear pending signals and get the process signal mask. */
 	sigemptyset(&_thr_proc_sigpending);