From owner-freebsd-threads@FreeBSD.ORG  Sun Jul 25 02:45:35 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 404F316A4CE
	for <freebsd-threads@freebsd.org>;
	Sun, 25 Jul 2004 02:45:35 +0000 (GMT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D140B43D3F
	for <freebsd-threads@freebsd.org>;
	Sun, 25 Jul 2004 02:45:34 +0000 (GMT)
	(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 i6P2jVjh014243;
	Sat, 24 Jul 2004 22:45:31 -0400 (EDT)
Date: Sat, 24 Jul 2004 22:45:31 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Jake Hamby <jhamby@anobject.com>
In-Reply-To: <41029703.8030008@anobject.com>
Message-ID: <Pine.GSO.4.10.10407242241380.12960-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-threads@freebsd.org
Subject: Re: pthread assertion failure in function _lock_acquire
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: Sun, 25 Jul 2004 02:45:35 -0000

On Sat, 24 Jul 2004, Jake Hamby wrote:

> Hi all,
> 
> I tried to build MonoDoc-1.0 using the port of mono-1.0 and -current
> (__FreeBSD_version 502123) and got this error right at the beginning of
> the build:
> 
> Assertion failed: (lu->lu_myreq->lr_owner == lu), function
> _lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 171.
> 
> The complete make output is attached below.  My CFLAGS settings are:
> 
> CPUTYPE?=p4
> CFLAGS= -O2 -pipe
> 
> Any ideas?  I filed this as bug "ports/69404".

Yes, something seems wrong with the application.  It's hitting code
that should never be hit.  We do not use any LCK_PRIORITY locks.
I suspect something is accessing memory after it has been deallocated.

You might also try 'ldd' on the executable to make sure it is only
linked to one threads library, and that it isn't statically allocating
LDTs (look for kernel warnings).

-- 
Dan Eischen