From owner-freebsd-threads@FreeBSD.ORG Sun Mar 14 18:38:34 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 024C816A4CE for ; Sun, 14 Mar 2004 18:38:34 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E6CD43D39 for ; Sun, 14 Mar 2004 18:38:33 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 75931 invoked from network); 15 Mar 2004 02:38:32 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 15 Mar 2004 02:38:32 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 14 Mar 2004 20:38:31 -0600 (CST) From: Mike Silbersack To: threads@freebsd.org Message-ID: <20040314203311.L19819@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Mutex unlock failure: ? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 02:38:34 -0000 I was just trying to build kdepim, and the following just occured: /usr/X11R6/bin/moc itemAttributeDialog.h -o itemAttributeDialog.moc rm -f itemAttributeDialog.cpp echo '#include ' > itemAttributeDialog.cpp /usr/X11R6/bin/uic -L /usr/local/lib/kde3/plugins/designer -nounload -tr tr2i18n -i itemAttributeDialog.h ./itemAttributeDialog.ui > itemAttributeDialog.cpp.temp ; ret=$?; \ /usr/local/bin/perl -pe "s,tr2i18n( \"\" ),QString::null,g" itemAttributeDialog.cpp.temp | /usr/local/bin/perl -pe "s,tr2i18n( \"\"\, \"\" ),QString::null,g" | /usr/local/bin/perl -pe "s,image([0-9][0-9]*)_data,img\$1_itemAttributeDialog,g" >> itemAttributeDialog.cpp ;\ rm -f itemAttributeDialog.cpp.temp ;\ if test "$ret" = 0; then echo '#include "itemAttributeDialog.moc"' >> itemAttributeDialog.cpp; else rm -f itemAttributeDialog.cpp ; exit $ret ; fi Mutex unlock failure: Operation not permitted And when I check in top, uic is just eating cpu time. Is this possibly some thread bug? I haven't recompiled X11 in quite a while, so it was probably built against libc_r, not libpthread. (I'm using libmap to remap libc_r to libpthread, FWIW.) Is that mutex unlock failure message something from libpthread? Is this a known bug of some sort in X11 or libpthread? Thanks, Mike "Silby" Silbersack