Wow, you guys have been busy while I was asleep! Thanks for the
reports, and for the diagnosis already done by Marcel, Luoqi, and
others.
If you are stuck with a kernel that can't run CVSup, I believe you can
work around the problem by adding "@M3novm" to the cvsup command line.
Add it anywhere
On Mon, 4 Oct 1999, 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
John,
> Also, for those of you who are experiencing problems: Please state
> as precisely as possible:
I have Oct 4 9pm PDT -current on K6 and SMP PPro machine.
CVSup coredumps on K6 machine reliably(?) but it works on
SMP PPro machine. I tried both 16.0/15.2(? previous one) packages.
Both ar
John Polstra <[EMAIL PROTECTED]> writes:
> 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
Fwiw, the problem seems to have disappeared over here. I'll check at home
later.
FreeBSD hal.mpn.cp.philips.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Oct 5
09:36:29 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/HAL
i386
Cheers,
--
Jos Backus _/ _/_/_/ "Reliab
Just an anti-me too.
Static cvsup works perfectly for me (installed from ports cvsup-bin on
Sept 9th).
I run it both on my dumb terminal and on my X display.
(My X configuration is XFree86 3.3.5, Gnome/Enlightenment [all built
Sept 9th after a make world]).
My shell is tcsh 6.09 (built Sept 1
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.
I received 3 reports on cvsup dumping core. At least 2 involved static
aout binaries. The third was solved by changing which s
On Tue, Oct 05, 1999 at 08:33:54AM +0200, Mark Murray <[EMAIL PROTECTED]> 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
> > bin
> 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. Coul
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'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
On Fri, Oct 01, 1999 at 05:57:14PM -0500, Chris Costello wrote:
>Try ``gdb cvsup cvsup.core''
jos:/tmp# file cvsup.core
cvsup.core: lif file
jos:/tmp# gdb /usr/local/bin/cvsup cvsup.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU Genera
I updated yesterday, installed the world and a new kernel. That all
worked. Today when I run cvsup with the same supfile I used yesterday
I get a core dump:
# cvsup /root/current-supfile
***
*** runtime error:
***Segmentation violation - possible attempt to dereference NIL
***
Abort tra
On Fri, Oct 01, 1999, Leonard Sitongia wrote:
> # gdb cvsup.core
> GNU gdb 4.18
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "sho
Leonard Sitongia wrote:
>
> Is there a new static binary to use?
>
No. Using an old one should fix this.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
15 matches
Mail list logo