Mutex unlock failure: ?
Mike Silbersack
silby at silby.com
Sun Mar 14 18:38:34 PST 2004
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 <klocale.h>' > 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
More information about the freebsd-threads
mailing list