From owner-freebsd-current@FreeBSD.ORG Tue Jun 17 16:35:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 227DD1065679 for ; Tue, 17 Jun 2008 16:35:23 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.79]) by mx1.freebsd.org (Postfix) with ESMTP id 06A338FC29 for ; Tue, 17 Jun 2008 16:35:22 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp015.mac.com (asmtp015-bge351000 [10.150.69.78]) by smtpoutm.mac.com (Xserve/smtpout016/MantshX 4.0) with ESMTP id m5HGZMrx006187; Tue, 17 Jun 2008 09:35:22 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp015.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K2M007418QYBQN5@asmtp015.mac.com>; Tue, 17 Jun 2008 09:35:22 -0700 (PDT) Message-id: From: Marcel Moolenaar To: Pietro Cerutti In-reply-to: <485779C3.8010302@FreeBSD.org> Date: Tue, 17 Jun 2008 09:35:21 -0700 References: <485779C3.8010302@FreeBSD.org> X-Mailer: Apple Mail (2.924) Cc: freebsd-current , freebsd-sparc64@freebsd.org Subject: Re: sh seg-faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 16:35:23 -0000 On Jun 17, 2008, at 1:45 AM, Pietro Cerutti wrote: > I'm experiencing "random" sh core-dumps while building ports. During > these core-dumps, sh is usually invoked by libtool. Pietro, I've seen something on PowerPC as well. If I recompile libc with lower optimization, the problem goes away (I think -O1 does the trick -- if not try -O0 :-). In particular, if you recompile lib/libc/gen/exec.c at -O the problem goes away. Everytime I've seen execvp() being the at the top of the call-chain. Can you check if it's execvp() for you as well? Thanks, -- Marcel Moolenaar xcllnt@mac.com