From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 13 01:50:51 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D447137B414; Wed, 13 Aug 2003 01:50:48 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4518B43FAF; Wed, 13 Aug 2003 01:50:47 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta03-svc.ntlworld.comESMTP <20030813085046.PFMG14590.mta03-svc.ntlworld.com@llama.fishballoon.org>; Wed, 13 Aug 2003 09:50:46 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19mrKQ-0008HH-CG; Wed, 13 Aug 2003 09:49:58 +0100 Date: Wed, 13 Aug 2003 09:49:58 +0100 From: Scott Mitchell To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org Message-ID: <20030813084958.GC31320@llama.fishballoon.org> References: <200307251450.h6PEo6XT080320@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307251450.h6PEo6XT080320@freefall.freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: scott+freebsd@fishballoon.org Subject: Re: bin/54854: cvs pserver sig11 crash on 4.8-R X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2003 08:50:52 -0000 Still seeing these crashes with a stock cvs 1.11.6 (ie. without any of the FreeBSD extension). The stack traces are very similar - it's interesting to note that the crash seems to be triggered by bad cleanup from a SIGPIPE, which I guess is related to the client-server connection closing down... Anyway, it looks less likely that this is a FreeBSD problem, although I still don't have any kind of solution other than using the binary from 4.6. We're planning to swap out the RAM in this machine within the next couple of weeks and run all the memory tests again, plus try all the versions of cvs we've built, in case this changes anything. Cheers, Scott