From owner-freebsd-threads@FreeBSD.ORG  Sun Mar 14 18:52:11 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 D328016A4CF
	for <threads@freebsd.org>; Sun, 14 Mar 2004 18:52:11 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 54EEC43D2F
	for <threads@freebsd.org>; Sun, 14 Mar 2004 18:52:11 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 81308 invoked from network); 15 Mar 2004 02:52:10 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 15 Mar 2004 02:52:10 -0000
X-pair-Authenticated: 209.68.2.70
Date: Sun, 14 Mar 2004 20:52:09 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: threads@freebsd.org
In-Reply-To: <20040314203311.L19819@odysseus.silby.com>
Message-ID: <20040314204754.I19819@odysseus.silby.com>
References: <20040314203311.L19819@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Mutex unlock failure:  ?
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2004 02:52:11 -0000


On Sun, 14 Mar 2004, Mike Silbersack wrote:

> 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

Hrm, looks like uic is part of qt, not X11.  So that rules out libc_r
interference.

Can someone else try building kdepim with libpthread and see what happens?

Mike "Silby" Silbersack