From owner-freebsd-current@FreeBSD.ORG Tue Jul 15 12:40:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14A1937B401; Tue, 15 Jul 2003 12:40:29 -0700 (PDT) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D6C743F75; Tue, 15 Jul 2003 12:40:27 -0700 (PDT) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h6FJeMv05234; Tue, 15 Jul 2003 21:40:22 +0200 (MEST) Date: Tue, 15 Jul 2003 21:40:22 +0200 (CEST) From: Harti Brandt To: Thomas Moestl In-Reply-To: <20030715193518.GA1660@crow.dom2ip.de> Message-ID: <20030715213656.A25192@beagle.fokus.fraunhofer.de> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715193518.GA1660@crow.dom2ip.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Dag-Erling Sm?rgrav cc: sparc64@freebsd.org cc: current@freebsd.org cc: Marcel Moolenaar Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Jul 2003 19:40:29 -0000 On Tue, 15 Jul 2003, Thomas Moestl wrote: TM>On Tue, 2003/07/15 at 12:04:56 -0700, Marcel Moolenaar wrote: TM>> On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote: TM>> > Marcel Moolenaar writes: TM>> > > It needs to be analyzed because cross-builds should not fail. Do TM>> > > we have a machine problem? What exactly is dumping core? Is it TM>> > > gzip or some binary started immediately after it? If it's gzip, TM>> > > is there a relation with the recent compiler warning about strncmp? TM>> > TM>> > It's not a machine problem if it only happens to the sparc64 build - TM>> > the same machine runs all the other -CURRENT tinderboxen except TM>> > powerpc. TM>> TM>> It does not only happen to sparc64. I've seen it fail for all but TM>> i386 and pc98, I think. TM> TM>i386 and pc98 have failed too (random example: July 5). But sparc64 fails quite regularily when gziping man pages. The others are more random. Since about the same time I have dumping core make during make universe on my i386. The core shows differnt signals (4, 10, even SIGILL), but always in vfork(). harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org