Date: Thu, 19 Feb 2004 14:24:36 -0600 From: "Guy Helmer" <ghelmer@palisadesys.com> To: <freebsd-current@freebsd.org> Subject: LinuxThreads and -current - stuck waiting to lock unlocked mutexes Message-ID: <FPEBKMIFGFHCGLLKBLMMCEPBCDAA.ghelmer@palisadesys.com>
next in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FPEBKMIFGFHCGLLKBLMMCEPBCDAA.ghelmer>