Date: Tue, 15 Jul 2003 21:40:22 +0200 (CEST) From: Harti Brandt <brandt@fokus.fraunhofer.de> To: Thomas Moestl <t.moestl@tu-bs.de> Cc: Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64 Message-ID: <20030715213656.A25192@beagle.fokus.fraunhofer.de> In-Reply-To: <20030715193518.GA1660@crow.dom2ip.de> References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org> <xzp65m3vfw1.fsf@dwp.des.no><xzpy8yzty2m.fsf@dwp.des.no> <20030715193518.GA1660@crow.dom2ip.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <marcel@xcllnt.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715213656.A25192>