Thanks for your advise Larry, I'll try. Moises. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 2:44 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Terminated with fatal signal 4
Zanabria, Moises writes: > > Checking in JP/main/Resource.h; > /cvsrepository/JP/main/Resource.h,v <-- Resource.h > new revision: 1.13; previous revision: 1.12 > done > Terminated with fatal signal 4 > cvs commit: saving log message in C:\DOCUME~1\admin\LOCALS~1\Temp\1\4 That indicates that the server subprocess crashed. On my system, signal 4 is SIGILL (illegal instruction), which implies some kind of memory corruption. If you can reproduce the problem with tracing enabled (the global -t option), the output might provide more clues as to what's going wrong. If you can manage to attach a debugger to the process (see the $CVS_SERVER_SLEEP environmnent variable), that would be even better. -Larry Jones We seem to be out of gun powder. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
