From owner-freebsd-current  Tue Oct 31 10:16:28 2000
Delivered-To: freebsd-current@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 325BF37B4C5; Tue, 31 Oct 2000 10:16:25 -0800 (PST)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA21123;
	Tue, 31 Oct 2000 10:16:12 -0800 (PST)
	(envelope-from jdp@wall.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.11.0/8.11.0) id e9VIGBc04408;
	Tue, 31 Oct 2000 10:16:11 -0800 (PST)
	(envelope-from jdp)
Date: Tue, 31 Oct 2000 10:16:11 -0800 (PST)
Message-Id: <200010311816.e9VIGBc04408@vashon.polstra.com>
To: current@freebsd.org
From: John Polstra <jdp@polstra.com>
Cc: dave@dogwood.com, obrien@freebsd.org
Subject: Re: threaded python seg faults?
In-Reply-To: <200010310535.e9V5Zhi25700@white.dogwood.com>
References: <200010310535.e9V5Zhi25700@white.dogwood.com>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <200010310535.e9V5Zhi25700@white.dogwood.com>,
Dave Cornejo  <dave@dogwood.com> wrote:
> For the last couple of days I've been trying to build python 2 from
> the ports tree without success.  I updated my sources a couple of time
> and rebuilt the kernel and world with no effect.
> 
> The problem seems to have appeared in the last couple of days and
> seems to happen while loading libc_r.so.4 - Is anyone else seeing
> this, or have any suggestion what I might be doing wrong?
[...]
> Program received signal SIGSEGV, Segmentation fault.
> 0x28383ec6 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
> (gdb) bt
> #0  0x28383ec6 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
> #1  0x80bb5b0 in __register_frame_info ()
> #2  0x2834713a in _init () from /usr/lib/libc_r.so.4
> #3  0x28343fe5 in _init () from /usr/lib/libc_r.so.4
> #4  0x2815086c in _rtld () from /usr/libexec/ld-elf.so.1

It's because libc_r isn't getting initialized in time.

Please try applying the appended patch to "src/gnu/lib/libgcc_r/Makefile"
and let us know if it fixes the problem.  You will need to rebuild
and reinstall libgcc_r, and then rebuild python.

Thanks for providing the detailed information!  This never would
have caught my eye otherwise.

John


Index: Makefile
===================================================================
RCS file: /home/ncvs/src/gnu/lib/libgcc_r/Makefile,v
retrieving revision 1.4
diff -u -r1.4 Makefile
--- Makefile	1999/10/03 02:43:20	1.4
+++ Makefile	2000/10/31 18:06:34
@@ -2,5 +2,6 @@
 
 LIB=	gcc_r
 CFLAGS+=-D_PTHREADS
+CFLAGS+=-D'__GTHREAD_MUTEX_INIT_FUNCTION(m)=pthread_mutex_init(m, NULL)'
 
 .include "../libgcc/Makefile"





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message