This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
CVS crashed on me, now I can't commit
- To: egcs-patches at egcs dot cygnus dot com
- Subject: CVS crashed on me, now I can't commit
- From: craig at jcb-sc dot com
- Date: 22 Feb 1999 13:46:36 -0000
- Cc: law at cygnus dot com
- Cc: craig at jcb-sc dot com
Looks like there's at least one bug in CVS. It crashed on me due
to some trivial bug, but, more worrisome, the *server* seems to have
no ability to intelligently recover when a *client* crashes (which
I would think includes a badly timed network outage).
Could someone at Cygnus fix this, or let me know how I can? (Looking
up "lock" in the man page didn't show anything obvious.)
tq vm, (burley)
[craig@deer cvs]$ cygcvs diff -p2N egcs/gcc/varasm.c > P0
Enter passphrase for RSA key 'craig@jcb-sc.com': *****
diff: context length specified twice
Terminated with fatal signal 11
Core dumped; preserving /tmp/cvs-serv20529 on server.
CVS locks may need cleaning up.
[craig@deer cvs]$ ls -l /tmp/cvs*
-rw-r--r-- 1 craig develop 306 Feb 14 04:38 /tmp/cvs01668aaa
[craig@deer cvs]$ cygcvs diff egcs/gcc/varasm.c > P0
Enter passphrase for RSA key 'craig@jcb-sc.com': *****
[craig@deer cvs]$ cygcvs commit -m "fix -fsyntax-only ICEs" egcs/gcc/ChangeLog egcs/gcc/varasm.c
Enter passphrase for RSA key 'craig@jcb-sc.com': *****
cvs server: [05:40:06] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
cvs server: [05:40:36] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
cvs server: [05:41:06] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
cvs server: [05:41:36] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
cvs server: [05:42:06] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
cvs server: [05:42:36] waiting for burley's lock in /egcs/carton/cvsfiles/egcs/gcc
Killed by signal 2.
cvs [commit aborted]: received interrupt signal
[craig@deer cvs]$