[-CURRENT tinderbox] failure on sparc64/sparc64
kris at obsecurity.org
Tue Jul 15 18:09:17 PDT 2003
On Tue, Jul 15, 2003 at 09:35:18PM +0200, Thomas Moestl wrote:
> On Tue, 2003/07/15 at 12:04:56 -0700, Marcel Moolenaar wrote:
> > On Tue, Jul 15, 2003 at 09:00:17PM +0200, Dag-Erling Sm?rgrav wrote:
> > > Marcel Moolenaar <marcel at 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.
> i386 and pc98 have failed too (random example: July 5).
> - Thomas
It's been doing this for weeks now. I wonder if this is a malloc
debugging problem that was introduced somehow.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20030715/69f408a5/attachment.bin
More information about the freebsd-sparc64