My machine is dual boot and I don't have time to reboot now. (I need to get
some sleep.) I'll provide what information I can quickly and will test things
further tomorrow evening.
I was seeing the core dumps from gui cvsup. My current was a couple different
cvsup runs on Saturday and Sunday. I am using the static binary installed from
the ports collection. I don't have a date or version right now, but seem to
recall it being 16.0. As others have mentioned, running cvsup under truss
works.
I'll let you know more tomorrow night if there is anything I can add.
Jim Bloom
[EMAIL PROTECTED]
John Polstra wrote:
>
> I've seen a few reports that CVSup has suddenly started dumping
> core on a segmentation violation under -current, but I need more
> information. For starters, I would like to know whether the static
> binary (ports/net/cvsup-bin) works or not under the very latest
> -current on the i386. Could somebody please check that and report
> back to the list? I can't sacrifice my i386 -current machine to the
> cause right now.
>
> Also, for those of you who are experiencing problems: Please state
> as precisely as possible:
>
> - which vintage of -current are you running?
> - what is the output from "cvsup -v"?
> - is "cvsup" a static binary or is it dynamically linked?
> - did you build it, or did you simply install a binary?
> - if you built it, when did you build it?
>
> Note, you are going to have trouble getting much out of the core dumps
> from the binaries, because they're a.out. I've placed an unstripped
> ELF binary here if you'd like to help out by getting a stack trace:
>
> http://www.freebsd.org/~jdp/cvsup-16.0.gz
>
> The compressed file is about 2.3 MB in size.
>
> John
> --
> John Polstra [EMAIL PROTECTED]
> John D. Polstra & Co., Inc. Seattle, Washington USA
> "No matter how cynical I get, I just can't keep up." -- Nora Ephron
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
