[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On update: end of file from server, no messages given

From: Larry Jones
Subject: Re: On update: end of file from server, no messages given
Date: Fri, 13 Jun 2003 11:14:13 -0400 (EDT)

Keane, Patrick writes:
> Is there a preferred method for debugging the server messages when an error
> occurs?  I am assuming (perhaps incorrectly) that the server is crashing
> halfway through file transfer (maybe SEGV).  What I need to understand is
> the reason.  We seem to have sufficient amounts of physical memory, and an
> abundance of virtual memory that remains unused during the transfer (watch
> cat /proc/meminfo shows this).

If the server is crashing, it should be leaving its temp directory
behind -- look for a core dump that you can examine with your favorite
debugger.  If you can reproduce the problem running in local mode on the
server, debugging is very easy.  If not, try to reproduce it using
:fork: mode on the server.  If you can do that, you can set the
$CVS_SERVER_SLEEP environment variable to give yourself time to connect
to the server process with a debugger.

Note that having lots of available memory doesn't mean that processes
are allowed to use it. I'm not familiar with Linux, but there are almost
certainly system limits on the amount of memory a single process is
allowed to use.  You should investigate what they are and how to change

-Larry Jones

How many presents do you think I'd forfeit for just one
clean smack upside Susie's head? -- Calvin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]