More modern systems sometimes leave a file named core.PID, where PID is a number. There may be other variations. I usually search for `*core*'. Some systems need the command `ulimit -c unlimited' run before the program which dumps core, though probably the default may be changed to unlimited via some system pref parameter somewhere.
A CVS server would most likely be leaving the cores under a directory under /tmp named `cvs-servXXXXXX', where XXXXXX is a random combination of letters and numbers. Normally CVS will remove the server tmp directory, but it isn't supposed to after a core dump. I can't do a whole lot without a core dump. If none of the above work for you, it is also possible to set "CVS_SERVER_SLEEP" to some number of seconds on the server (most likely in inetd, xinetd, or a cvs server wrapper script), then quickly connect to the server process using a debugger while it sleeps, after starting it via Tortoise or whatever. Good luck, Derek Gary Wake wrote: > Love to but we don't have a 'core' file anywhere on the system > > Derek Price wrote: > >> Gary Wake wrote: >> >> >> >>> Terminated with fatal signal 11 >>> >>> Error, CVS operation failed >>> >> >> >> >> Can you find the server core dump and get us a stack trace from the >> debugger? >> >> Regards, >> >> Derek >> >> >> >> _______________________________________________ >> Bug-cvs mailing list >> Bug-cvs@gnu.org >> http://lists.gnu.org/mailman/listinfo/bug-cvs >> >> > > ------------------------------- > This email message and any attachment(s) is intended only for the > person(s) or entity(entities) to whom it is addressed. The information > it contains may be classified as IN CONFIDENCE and may be > legally privileged. If you are not the intended recipient any use, > disclosure or copying of the message or attachment(s) is strictly > prohibited. If you have received this message in error please notify > us immediately and destroy it and any attachment(s). > Thank you. The Ministry of Social Development accepts no > responsibility for changes made to this message or to any > attachment(s) after transmission from the Ministry. > ------------------------------- > _______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs