bug-cvs
[Top][All Lists]
Advanced

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

Re: cvs 1.11.5 pserver sig11 crash on FreeBSD 4.8-R


From: Mark D. Baushke
Subject: Re: cvs 1.11.5 pserver sig11 crash on FreeBSD 4.8-R
Date: Tue, 29 Jul 2003 03:32:30 -0700

Scott Mitchell <address@hidden> writes:

> On Sun, Jul 27, 2003 at 01:21:23PM -0700, Mark D. Baushke wrote:
> > It would be useful if you could try using the cvs-1.11.6 or cvs-1.12.1
> > release from cvshome.org to see if it has the same problems. It would
> > also be useful to know if the clients that are having the problems are
> > at the same basic release as the server or not.
> 
> A lot of the clients, especially the Windows ones, will still be running
> 1.10.  We don't need any of the FreeBSD extensions with this repository,
> so I should be able to try 1.11.6 and 1.12.1 without breaking anything.
> We're right at the end of a release cycle just now, so I can't touch
> anything before next week, and I plan to run some more RAM diagnostics on
> the server before I start messing with the software.

Hmmm... 1.10 is ancient, but most stuff should work fine (deletion of a 
branch tag will fail because the client will not be able to send the -B
switch, but other than that things should just work).

If you have any possibility of upgrading to a more recent vintage, there
were a lot of bugs fixed...

> > It would be good to know at least one of the client side configurations
> > that cause the core dump on the server. It might be useful to also do
> > a correlation to see if the same client version caused all of the server
> > core dumps.
> 
> The two clients that I'm certain have triggered server-side core dumps
> are 1.10 on a Win2K box and 1.11.1p1 on a Debian (2.4.18 kernel) box.
> All I get is a core and a UID in the logs, so unless I actually see it
> happen and grab the user right then to see what they sere doing, I've no
> way of knowing which client machine was the culprit :-(
> 
> Thanks for the feedback.  I'll see if I can get one or both of those newer
> versions compiled and try them out next week.

Well, it sounds like a fairly nasty situation. I wish you well in
tracking down the problem.

        Good luck,
        -- Mark




reply via email to

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