Hi I believe this is caused by the pre-released version of gcc in the system.
I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Good-luck, kt On Wed, Aug 21, 2002 at 05:27:24PM +0200, Martin Blapp wrote: > > Hi, > > > > The 2nd one fails at exactly the same point, that can't be coindedence. > > > Also with a signal 10. (libutil) > > > > > > The 3rd ended somewhere else(games/rogue), but now with signal 4. > > > > > > Doing the 4rd now. > > > > Which ends with signal 11 in usr.sbin/devinfo/ ... > > > > Mark > > May this be the memory corruption other users see (Alfred, David) ? > > I'll start again a new row of 10 builds here and see where it > ends. > > Martin > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
