From owner-freebsd-threads@FreeBSD.ORG  Sun Mar 14 20:35:48 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 A83A616A4CE
	for <threads@freebsd.org>; Sun, 14 Mar 2004 20:35:48 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2295043D3F
	for <threads@freebsd.org>; Sun, 14 Mar 2004 20:35:48 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i2F4ZlW7013743;
	Sun, 14 Mar 2004 23:35:47 -0500 (EST)
Date: Sun, 14 Mar 2004 23:35:47 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Mike Silbersack <silby@silby.com>
In-Reply-To: <20040314204754.I19819@odysseus.silby.com>
Message-ID: <Pine.GSO.4.10.10403142335020.12209-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: threads@freebsd.org
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 04:35:48 -0000

On Sun, 14 Mar 2004, Mike Silbersack wrote:

> 
> 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?

I built kdepim-3.2.0_1 a week or two ago and it built fine (libc_r ->
libpthread).

-- 
Dan Eischen