From owner-freebsd-stable@FreeBSD.ORG Tue Sep 7 02:51:35 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6944A16A4CE for ; Tue, 7 Sep 2004 02:51:35 +0000 (GMT) Received: from mta2.srv.hcvlny.cv.net (mta2.srv.hcvlny.cv.net [167.206.5.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2959A43D1F for ; Tue, 7 Sep 2004 02:51:35 +0000 (GMT) (envelope-from sahil@hamla.org) Received: from [192.168.1.101] (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta2.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I3N00FD6H7XAJ@mta2.srv.hcvlny.cv.net> for freebsd-stable@freebsd.org; Mon, 06 Sep 2004 22:50:21 -0400 (EDT) Date: Mon, 06 Sep 2004 22:49:56 -0400 From: Sahil Tandon In-reply-to: <200409052337.01634.kstewart@owt.com> To: freebsd-stable@freebsd.org Message-id: <413D21D4.9070109@hamla.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) References: <413BC4CD.5090201@hamla.org> <200409061533.39374.doconnor@gsoft.com.au> <413BFFD7.50503@mcsi.pp.ru> <200409052337.01634.kstewart@owt.com> cc: Maxim Maximov cc: kstewart Subject: Re: portsdb -Uu results in coredump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 02:51:35 -0000 kstewart wrote: > There is a bug in ruby that shows up as a bus error. Follow the topic on > -ports@. There are several ways to alter the INDEX[-5] so that it occurs less > frequently. Occurs less frequently? That's not what I'm looking for. Is there a *fix* for the root cause? > I started using portindexdb because it doesn't error off. I also don't use > categories, which it doesn't produce. I'm using portsindexsb as a work around, but it still doesn't address or solve the problem which makes portsdb -Uu fail. I've tried removing and re-extracting the ports tree and doing whatever else was suggested in the -ports@ mailing list(s) - to no avail.