LinuxThreads and -current - stuck waiting to lock unlocked mutexes

On a related note to a previous message regarding threads and -current, I've
rebuilt my application using LinuxThreads and I'm able to "kill -ABRT" each
of the "threads" (really processes) and obtain coredumps to debug a
threading problem.

What I'm finding is that each of the threads is becoming stuck in a similar
fashion, at sigsuspend / pthread_wait_for_restart_signal /
pthread_suspend_old / pthread_alt_lock / pthread_mutex_lock:

(gdb) where
#0  0x281568e7 in sigsuspend () from /lib/libc.so.5
#1  0x28102265 in __pthread_wait_for_restart_signal ()
   from /usr/local/lib/liblthread.so.3
#2  0x28102364 in __pthread_suspend_old () from
/usr/local/lib/liblthread.so.3
#3  0x280ff8ec in __pthread_alt_lock () from /usr/local/lib/liblthread.so.3
#4  0x28102b22 in pthread_mutex_lock () from /usr/local/lib/liblthread.so.3
#5  0x0804a695 in xxx_advance_seconds (pbw=0x80ad180, ns=1077221144) at
xxx.c:80

but no other thread owns the mutex.  Is this symptomatic of lost signals?

Thanks,
Guy

Guy Helmer, Ph.D., Principal System Architect, Palisade Systems, Inc.
http://www.palisadesys.com/~ghelmer/