Date: Tue, 15 Jul 2003 12:04:56 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Dag-Erling Sm?rgrav <des@des.no> Cc: sparc64@freebsd.org Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 Message-ID: <20030715190456.GC15674@dhcp01.pn.xcllnt.net> In-Reply-To: <xzpy8yzty2m.fsf@dwp.des.no> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <20030715175821.K34004@beagle.fokus.fraunhofer.de> <xzp65m3vfw1.fsf@dwp.des.no> <20030715185438.GB15674@dhcp01.pn.xcllnt.net> <xzpy8yzty2m.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote: > Marcel Moolenaar <marcel@xcllnt.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715190456.GC15674>