From owner-freebsd-ports@FreeBSD.ORG  Wed Apr 30 16:35:17 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3BC711065674
	for <ports@FreeBSD.org>; Wed, 30 Apr 2008 16:35:17 +0000 (UTC)
	(envelope-from jasone@FreeBSD.org)
Received: from canonware.com (canonware.com [64.183.146.166])
	by mx1.freebsd.org (Postfix) with ESMTP id 1A2488FC15
	for <ports@FreeBSD.org>; Wed, 30 Apr 2008 16:35:17 +0000 (UTC)
	(envelope-from jasone@FreeBSD.org)
Received: from [192.168.168.201] (unknown [192.168.168.201])
	by canonware.com (Postfix) with ESMTP id 0E0711298E6;
	Wed, 30 Apr 2008 09:36:08 -0700 (PDT)
Message-ID: <48189FC3.4010701@FreeBSD.org>
Date: Wed, 30 Apr 2008 09:35:15 -0700
From: Jason Evans <jasone@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Eric Schuele <e.schuele@computer.org>
References: <4812AC7C.5050202@computer.org> <48164221.6000704@FreeBSD.org>
	<4818977B.3040202@computer.org>
In-Reply-To: <4818977B.3040202@computer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ports <ports@FreeBSD.org>
Subject: Re: Trouble building guile 1.8.4 (segfault in gen-scmconfig)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2008 16:35:17 -0000

Eric Schuele wrote:
> On 04/28/2008 16:31, Jason Evans wrote:
>> What is liblthread?  
> 
> linuxthreads, as Mezz mentioned.
> 
>> It looks to be interacting badly with malloc.
> 
> ok.  any thoughts as to why, or how to fix it?

Most likely, the linuxthreads port is allocating memory within one of 
the pthread_mutex-related functions (pthread_mutex_init()?), which is 
causing infinite recursion.  The easy solution is to stop using 
linuxthreads.  The hard solution is to modify linuxthreads, possibly by 
implementing _pthread_mutex_init_calloc_cb(), in order to avoid 
recursion during initialization of malloc's internal mutexes.

Jason