On Tue, 12 Sep 2000, John Polstra wrote:
> Date: Tue, 12 Sep 2000 12:51:15 -0700 (PDT)
> From: John Polstra <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: ports cvsup
>
> In article <[EMAIL PROTECTED]>,
> Balis George <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> John D. Polstra & Co., Inc. Seattle, Washington USA
> "Disappointment is a good sign of basic intelligence." -- Ch&phgr;gyam Trungpa
>
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
//
//
*==============<<=============================================================>
\\
\\
When you gaze long into the abyss,
the abyss also gazes into you...
"Friedrich Nietzche"
\\
\\
<=============================================================>>==============*
//
//
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
