From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 12:24:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E67A16A4CE for ; Thu, 19 Feb 2004 12:24:38 -0800 (PST) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 126C043D2D for ; Thu, 19 Feb 2004 12:24:38 -0800 (PST) (envelope-from ghelmer@palisadesys.com) Received: from mira (mira.palisadesys.com [192.188.162.116]) (authenticated bits=0)i1JKObKw035150 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Thu, 19 Feb 2004 14:24:37 -0600 (CST) (envelope-from ghelmer@palisadesys.com) From: "Guy Helmer" To: Date: Thu, 19 Feb 2004 14:24:36 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: LinuxThreads and -current - stuck waiting to lock unlocked mutexes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 20:24:38 -0000 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/