> In article <[EMAIL PROTECTED]>, > Andrey A. Chernov <[EMAIL PROTECTED]> wrote: > > The bug completely gone after I revert machdep.c to 1.538. This commit > > cause bug: > > > > -------------------------------------------------------------------- > > revision 1.539 > > date: 2002/09/30 07:02:22; author: obrien; state: Exp; lines: +10 -0 > > Save the FP state in the PCB as that is compatable with releng4 binaries. > > > > This is a band-aid until the KSE pthread committers get back on the ground > > and have their machines setup. > > > > Submitted by: eischen > > -------------------------------------------------------------------- > > Good sleuthing! > > > Additional details: it cause not only cvsupd death, but rarely cvsup > > signal 6 death too with this diagnostic: > > > > *** > > *** runtime error: > > *** Value out of range > > *** file > > "/tmp/a/ports/lang/ezm3/work/ezm3-1.0/libs/libm3/src/uid/Common/Time > > Stamp.m3", line 63 > > This particular message is usually caused by a very bogus system date > setting.
I also see this on current using cvsup and my machine is synced with ntpd, so its time is ok. I have tried a few different versions of cvsup, but they all do the same thing. I have not tried to compile my own yet. In my case cvsup die everytime I try to use it. It go through the src but breaks somewhere in ports/math. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
