From owner-freebsd-questions@FreeBSD.ORG Tue Sep 7 00:35:02 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0151316A4CE for ; Tue, 7 Sep 2004 00:35:02 +0000 (GMT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CB5643D54 for ; Tue, 7 Sep 2004 00:35:01 +0000 (GMT) (envelope-from fj@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id C9DD948735 for ; Mon, 6 Sep 2004 20:35:00 -0400 (EDT) Received: (from fj@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i870Z0G11644 for freebsd-questions@freebsd.org; Mon, 6 Sep 2004 20:35:00 -0400 (EDT) Date: Mon, 6 Sep 2004 20:35:00 -0400 From: Joe Altman To: freebsd-questions@freebsd.org Message-ID: <20040907003500.GA11100@panix.com> Mail-Followup-To: Joe Altman , freebsd-questions@freebsd.org References: <7A727F81-FCE2-11D8-8BE7-000A95EFF4CA@foolishgames.com> <008901c4934e$a7c5b260$0200000a@SAGEAME> <413B5F14.6090405@zonnet.nl> <200409051452.06236.donaldj1066@fastmail.fm> <413C0FAE.1000502@zonnet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <413C0FAE.1000502@zonnet.nl> User-Agent: Mutt/1.4.2.1i Subject: Re: [another "me too"] Re: portindex/portindexdb X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 00:35:02 -0000 On Mon, Sep 06, 2004 at 09:20:14AM +0200, Nico Meijer wrote: > Hi Donald, > > >Nico - I suggest you try it again tomorrow. I thought I had it fixed > >yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is > >again seg faulting for me. Not going into a loop and continuously > >seg faulting, but bad enough. > > After cvsupping my ports tree, running portindex (not portindexdb!) and > portsdb -u (which gave core dumps) all is well. No more 'bus errors'. > > portindex seems like a wonderful tool, so I'm keeping it around. Sigh: on voip in /var/db # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait.. Done. done [Updating the portsdb in /usr/ports ... - 11736 port entries found .........1000.........2000.........3000.........4000......... 5000.........6000.........7000.........8000.... /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) I'm thinking, at this point, that I'm seeing something hardware-related. Good thing I'm replacing voip w/ new hardware and moving to 5.3, I guess.