Date: Wed, 13 Sep 2000 06:49:25 +0300 (EET DST) From: Balis George <cobra@ceid.upatras.gr> To: John Polstra <jdp@polstra.com> Cc: hackers@freebsd.org Subject: Re: ports cvsup Message-ID: <Pine.GSO.4.21.0009130645440.10015-100000@diogenis.ceid.upatras.gr> In-Reply-To: <200009121951.MAA67330@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Sep 2000, John Polstra wrote: > Date: Tue, 12 Sep 2000 12:51:15 -0700 (PDT) > From: John Polstra <jdp@polstra.com> > To: hackers@freebsd.org > Cc: cobra@ceid.upatras.gr > Subject: Re: ports cvsup >=20 > In article <Pine.GSO.4.21.0009072354500.20098-100000@diogenis.ceid.upatra= s.gr>, > Balis George <cobra@ceid.upatras.gr> wrote: > > The last days I am trying to cvs both the latest stable source and the > > latest ports from several servers. The problem is that when I am cvsing > > the ports I get a segmentation faults and cvsup exits ungracefully > > with a core dump. What could be wrong? > > I include some maybe helpful info > [...] > > achilles# /usr/local/bin/cvsup -g -L 2 /usr/local/etc/cvsup/freebsd-por= ts-supfile > > Parsing supfile "/usr/local/etc/cvsup/freebsd-ports-supfile" > > Connecting to cvsup3.FreeBSD.org > > Connected to cvsup3.FreeBSD.org > > Server software version: REL_16_1 > > Negotiating file attribute support > > Exchanging collection information > > Establishing multiplexed-mode data connection > > Running > > Updating collection ports-base/cvs > > Edit ports/INDEX > > Add delta 1.293 2000.09.05.19.23.28 asami > > Checkout ports/Mk/bsd.ruby.mk > > Edit ports/Mk/bsd.sites.mk > > Add delta 1.9 2000.09.05.01.04.52 steve > > Illegal instruction (core dumped) >=20 > Illegal instruction faults may indicate that a thread stack > overflowed, or they might be symptomatic of HW or kernel problems. > Does it always seem to fail at the same point in the update? Actually > it is hard to tell, since the log output only reflects what the > Updater thread is doing. >=20 > Here is what I would recommend. Make sure your kernel has "options > KTRACE" configured in. Run cvsup under "ktrace -t cnis", but also add > "@M3novm -P -" to the cvsup command line options. (If firewall issues > prevent that from working, try "@M3novm -P a" instead.) Do this a few > times, saving the "ktrace.out" file each time. Then use "kdump" to > generate printable output from each ktrace.out file. Send me the > last 500 lines of each one, and I'll try to figure out what's going > wrong. >=20 > If a thread stack is overflowing, it is probably caused by a corrupted > file. However, I would prefer that you let me analyze the problem > before you try to correct it by removing files, since it's a bug if > cvsup dumps core because of a bad file (or for any reason at all). >=20 > John > --=20 > John Polstra jdp@polstra.= com > John D. Polstra & Co., Inc. Seattle, Washington = USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam Tr= ungpa >=20 Thank you very much John but it seems that my problem got solved when i specified: ports-all instead of specifying individual ones. Also the core dump happened only when i was cvs-ing the ports not the system sources. So maybe there is a bug in the current cvsupd implementaion that I'm not aware of. In anycase I got my ports and I'm ok now but maybe I should check a little more on the matter. George =09=09 // =09=09// *=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D> =09=09\\ =09=09 \\ =09=09=09When you gaze long into the abyss,=20 =09=09=09the abyss also gazes into you... =09=09=09=09=09"Friedrich Nietzche" =09=09=09=09=09=09=09 \\ =09=09=09=09=09=09=09 \\ <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D* =09=09=09=09=09=09=09 // =09=09=09=09=09=09=09 // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0009130645440.10015-100000>