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 Message-ID: <200009121951.MAA67330@vashon.polstra.com> In-Reply-To: <Pine.GSO.4.21.0009072354500.20098-100000@diogenis.ceid.upatras.gr> References: <Pine.GSO.4.21.0009072354500.20098-100000@diogenis.ceid.upatras.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.GSO.4.21.0009072354500.20098-100000@diogenis.ceid.upatras.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-ports-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) 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. 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. 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). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa 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?200009121951.MAA67330>