Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Aug 2003 14:15:16 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Mike Silbersack <silby@silby.com>
Cc:        Bosko Milekic <bmilekic@technokratis.com>
Subject:   Re: cvs commit: src/sys/i386/i386 pmap.c
Message-ID:  <16178.38708.370002.463156@grasshopper.cs.duke.edu>
In-Reply-To: <20030807130312.X38264@odysseus.silby.com>
References:  <200308061846.h76IkmYp068237@repoman.freebsd.org> <20030806162243.A91712@grasshopper.cs.duke.edu> <3F3164D8.17704FF1@imimic.com> <16177.32077.922446.986623@grasshopper.cs.duke.edu> <20030806231310.GC46411@technokratis.com> <16178.19268.570629.572965@grasshopper.cs.duke.edu> <20030807104845.A93385@grasshopper.cs.duke.edu> <20030807130312.X38264@odysseus.silby.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Mike Silbersack writes:
 > 
 > On Thu, 7 Aug 2003, Andrew Gallatin wrote:
 > 
 > > It changed the failure somewhat.  Now make segfaults, and syntax
 > > errors which may not actually exist are found when building libstdc++.
 > >
 > > I'm going to back off to a known good kernel and make sure my srcs are
 > > not hosed.
 > >
 > > Drew
 > 
 > Are you sure this final bug isn't gcc's fault?  One of my machines has had
 > occasionaly buildworld failures in libstdc++, _but nowhere else_.  I was
 > even able to repeat the failure if I did make buildworld -DNOCLEAN.
 > 
 > (That doesn't cover make segfaulting, of course.)

I'm pretty sure.   The known good kernel (july 4th) just built the
world successfully with -j16.

I think I'm going to MFI386 Alan's pmap fix to pmap_insert_entry(),
that at least seems to help things out quite a bit.

I'm building now with an INVARIANTS/WITNESS kernel to see if its
perhaps related to  the memory-modified-after-free bug that somebody
(you?)  reported.

Drew



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16178.38708.370002.463156>