From owner-freebsd-ports@FreeBSD.ORG Fri Jul 11 18:37:07 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B251C1065675; Fri, 11 Jul 2008 18:37:07 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 117188FC19; Fri, 11 Jul 2008 18:37:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4877A84F.9030309@FreeBSD.org> Date: Fri, 11 Jul 2008 20:37:03 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: David Southwell References: <200807101120.41134.david@vizion2000.net> <20080711162439.06036517@peedub.jennejohn.org> <200807111005.11452.david@vizion2000.net> <200807111012.13653.david@vizion2000.net> In-Reply-To: <200807111012.13653.david@vizion2000.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , Shields , Wesley@freebsd.org, gary.jennejohn@freenet.de, freebsd-ports@freebsd.org Subject: Re: NOT SOLVED --cvsup after upgrade to 6.3 coredump X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 18:37:07 -0000 David Southwell wrote: > But this may be a clue > Here is what happened.. in the past it seemed to core dump immediately - but > now it transpires the dumping takes place only once the connection is made. I > incorrectly assumed all was OK when I got the "Rejected by Server" message > but jumped too quickly. So problem is still with us!! > > Connected to cvsup10.FreeBSD.org > Rejected by server: Access limit exceeded; try again later > Will retry at 10:05:05 > Retrying > Connected to cvsup10.FreeBSD.org > Bus error: 10 (core dumped) > [root@dns1 /usr/ports/net/cvsup-without-gui] > > Any ideas?? Can you either get a backtrace or do a binary search on the kernel sources to work out which commit caused it? Kris