From owner-freebsd-current@FreeBSD.ORG Tue Jul 15 12:05:07 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 6035C37B401; Tue, 15 Jul 2003 12:05:07 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D9E343FDD; Tue, 15 Jul 2003 12:05:06 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6FJ4uv1098888; Tue, 15 Jul 2003 12:04:56 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6FJ4uNd015774; Tue, 15 Jul 2003 12:04:56 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6FJ4uR7015773; Tue, 15 Jul 2003 12:04:56 -0700 (PDT) (envelope-from marcel) Date: Tue, 15 Jul 2003 12:04:56 -0700 From: Marcel Moolenaar To: Dag-Erling Sm?rgrav Message-ID: <20030715190456.GC15674@dhcp01.pn.xcllnt.net> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> <20030715185438.GB15674@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: current@freebsd.org cc: sparc64@freebsd.org 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:05:07 -0000 On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote: > Marcel Moolenaar writes: > > It needs to be analyzed because cross-builds should not fail. Do > > we have a machine problem? What exactly is dumping core? Is it > > gzip or some binary started immediately after it? If it's gzip, > > is there a relation with the recent compiler warning about strncmp? > > It's not a machine problem if it only happens to the sparc64 build - > the same machine runs all the other -CURRENT tinderboxen except > powerpc. It does not only happen to sparc64. I've seen it fail for all but i386 and pc98, I think. > There doesn't seem to be anything wrong with the sources > either. I tend to agree. > There's not much more I can say about it until I see the full > log from the next run; the last one broke at a different point. The first question is: what process is dumping core. I think you'll find that with dmesg(8). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net