From owner-freebsd-bugs Wed Sep 15 16:13:22 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from balsam.methow.com (balsam.methow.com [206.107.156.5]) by hub.freebsd.org (Postfix) with SMTP id 5BDEC14BE5 for ; Wed, 15 Sep 1999 16:13:18 -0700 (PDT) (envelope-from tcole@balsam.methow.com) Received: (qmail 25619 invoked by uid 535); 15 Sep 1999 23:13:19 -0000 Date: Wed, 15 Sep 1999 16:13:19 -0700 From: Travis Cole To: freebsd-bugs@FreeBSD.ORG Cc: Ruslan Ermilov , Dag-Erling Smorgrav Subject: Re: kern/13739: FreeBSD 3.3-RC panics durring make world Message-ID: <19990915161318.A25277@wcug.wwu.edu> References: <199909140150.SAA79522@freefall.freebsd.org> <19990914012514.A9665@wcug.wwu.edu> <19990914171707.A22136@wcug.wwu.edu> <19990915105654.I86648@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990915105654.I86648@relay.ucb.crimea.ua>; from Ruslan Ermilov on Wed, Sep 15, 1999 at 10:56:54AM +0300 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 15, 1999 at 10:56:54AM +0300, Ruslan Ermilov wrote: > > > > Also I don't get a panic every time. Sometimes I just get a lot of > > error, as if the code was broken and wouldn't compile, but always in > > different places. > > > Examples, examples! Ok, here are some I got today: cd /usr/src/lib/libtermcap; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/ src/tmp/usr/bin/make -B install cc -O -pipe -DCM_N -DCM_GT -DCM_B -DCM_D -I/usr/src/lib/libtermcap -I/usr/obj/us r/src/tmp/usr/include -c /usr/src/lib/libtermcap/termcap.c -o termcap.o cc -O -pipe -DCM_N -DCM_GT -DCM_B -DCM_D -I/usr/src/lib/libtermcap -I/usr/obj/us r/src/tmp/usr/include -c /usr/src/lib/libtermcap/tgoto.c -o tgoto.o stdin:1: parse error at null character /usr/src/lib/libtermcap/tgoto.c: In function `tgoto': /usr/src/lib/libtermcap/tgoto.c:103: parse error at null character *** Error code 1 And after a `make clean` I did another `make buildworld` and got: cc -pg -O -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/usr/src/tmp/usr/inclu de -c /usr/src/lib/libmytinfo/tgoto.c -o tgoto.po cc -pg -O -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/usr/src/tmp/usr/inclu de -c /usr/src/lib/libmytinfo/tiget.c -o tiget.po cc -pg -O -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/usr/src/tmp/usr/inclu de -c /usr/src/lib/libmytinfo/tmatch.c -o tmatch.po stdin:1: parse error at null character stdin:1564: Unterminated string constant *** Error code 1 > > > I never get sig11's or anything like that which > > would suggest hardware problems, but just panics or lots and lots > > of errors. Could those be caused by hardware problems? > > > Sure! Maybe your CPU is overlocked? Not overclocked. Probably my RAM :( But this RAM has been working with out a problem for 2 years. -- --Travis When it comes to violence, morality and the young, we're the Idiot Nation, the laughingstock not only of the civilized world but of the highly-wired generation of kids we're supposedly trying to protect. Jon Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message