From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: JD Smith Newsgroups: gmane.emacs.devel Subject: Re: CVS issues Date: Tue, 25 Apr 2006 10:42:37 -0700 Message-ID: <1145986957.3195.44.camel@turtle.as.arizona.edu> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1145987001 30038 80.91.229.2 (25 Apr 2006 17:43:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 Apr 2006 17:43:21 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 25 19:43:18 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FYRZ6-0002LX-0H for ged-emacs-devel@m.gmane.org; Tue, 25 Apr 2006 19:43:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYRZ5-0002L1-DI for ged-emacs-devel@m.gmane.org; Tue, 25 Apr 2006 13:43:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FYRYt-0002Kw-Eq for emacs-devel@gnu.org; Tue, 25 Apr 2006 13:42:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FYRYq-0002Kk-Kt for emacs-devel@gnu.org; Tue, 25 Apr 2006 13:42:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FYRYq-0002Kh-Fb for emacs-devel@gnu.org; Tue, 25 Apr 2006 13:42:52 -0400 Original-Received: from [128.196.210.37] (helo=nsa.as.arizona.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FYRbK-0003fI-Mj; Tue, 25 Apr 2006 13:45:27 -0400 Original-Received: from biff.as.arizona.edu (biff.as.arizona.edu [128.196.211.142]) by nsa.as.arizona.edu (8.13.6/8.13.6) with ESMTP id k3PHgWlP025888; Tue, 25 Apr 2006 10:42:32 -0700 Original-Received: from turtle.as.arizona.edu (turtle.as.arizona.edu [128.196.208.207]) by biff.as.arizona.edu (8.12.8/8.12.8) with ESMTP id k3PHgWmd006188; Tue, 25 Apr 2006 10:42:32 -0700 Original-To: rms@gnu.org In-Reply-To: X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) X-Scanned-By: MIMEDefang 2.42 X-so-MailScanner-Information: Please contact the ISP for more information X-so-MailScanner: Found to be clean X-so-MailScanner-SpamCheck: so1: not spam, SpamAssassin (score=-1.332, required 7.9, autolearn=disabled, ALL_TRUSTED -1.44, AWL 0.11) X-so-MailScanner-From: jdsmith@as.arizona.edu X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:53398 Archived-At: On Tue, 2006-04-25 at 12:48 -0400, Richard Stallman wrote: > With a recent build of CVS Emacs, I've experienced problems relating to > the "cvs" command in VC mode. E.g. C-x v l often results in: > > Process cvs killed > > Has there been any progress debugging this? > > Since this is not reproducible, I see only two ways to debug it: > > * Add code to record some history information that you could > look at after a failure. > > * Try building checkouts from various dates, hoping thus to determine > which change caused the problem. > > You recall approximately when you made a build that did not have this > problem? No progress here. I can only say for certain that 21.X did not show the problem (i.e., I'd experience the problem, run an old Emacs 21.4 on the same files, repeat the same commands, and have no problem). As far as I know, all versions since then are affected (though I have only experienced it in the last several months). I have not successfully reproduced it with Emacs from CVS since I reported it. The one potential silver lining is it seems to depend somehow on the session, such that once a cvs command fails, it is likely to fail again in that same Emacs session. This may in fact result from persistent external conditions, like the difficulty of SSH to connect to a CVS server, etc. If I encounter it again, I'll leave that session running and then we can consider how best to get to the bottom of it.