From owner-freebsd-current  Wed Nov  1  9:44:52 2000
Delivered-To: freebsd-current@freebsd.org
Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131])
	by hub.freebsd.org (Postfix) with ESMTP
	id 74F5237B479; Wed,  1 Nov 2000 09:44:41 -0800 (PST)
X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de)
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id eA1Hidl16692;
	Wed, 1 Nov 2000 18:44:39 +0100 (MET)
Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17])
	by mail1.siemens.de (8.11.0/8.11.0) with ESMTP id eA1Hick12221;
	Wed, 1 Nov 2000 18:44:38 +0100 (MET)
Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134])
	by mars.cert.siemens.de (8.11.1/8.11.1/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id eA1Hich00649;
	Wed, 1 Nov 2000 18:44:38 +0100 (CET)
Received: (from ust@localhost)
	by alaska.cert.siemens.de (8.11.1/8.11.1/alaska [ $Revision: 1.4 ]) id eA1Hicp02288;
	Wed, 1 Nov 2000 18:44:38 +0100 (CET)
	(envelope-from ust)
Date: Wed, 1 Nov 2000 18:44:38 +0100
From: Udo Schweigert <ust@cert.siemens.de>
To: Maxim Sobolev <sobomax@FreeBSD.ORG>
Cc: current@FreeBSD.ORG, jdp@FreeBSD.ORG, obrien@FreeBSD.ORG
Subject: Re: ABI is broken??
Message-ID: <20001101184438.A2269@alaska.cert.siemens.de>
References: <3A005026.47B9978C@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3A005026.47B9978C@FreeBSD.org>; from sobomax@FreeBSD.ORG on Wed, Nov 01, 2000 at 07:17:26PM +0200
X-Operating-System: FreeBSD 4.2-BETA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Nov 01, 2000 at 19:17:26 +0200, Maxim Sobolev wrote:
> Hi,
> 
> I'm not sure what exactly caused this behaviour (I can guess two potential
> victims: O'Brien's changes in crt stuff and recent Polstra's changes in
> libgcc_r), but it seems that some programs built on the previous -current from
> 27 October immediately segfault when I'm trying to run then on system installed
> from today's sources. The segfault disappeared when I recompiled affected
> program. With this message I'm attaching short backtrace.
> 
> -Maxim
> 
> #0  0x287de417 in pthread_mutex_lock () from /usr/lib/libc_r.so.4
> 

Same for me in -stable (4.2-BETA) and python-1.6. After rebuilding the port
this disappeared. My gdb showed the same error message as the quoted above.

Regards.
-- 
Udo Schweigert, Siemens AG   | Voice      : +49 89 636 42170
ZT IK 3, Siemens CERT        | Fax        : +49 89 636 41166
D-81730 Muenchen / Germany   | email      : ust@cert.siemens.de
PGP-2/5 fingerprint          | D8 A5 DF 34 EC 87 E8 C6  E2 26 C4 D0 EE 80 36 B2


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