Date: Mon, 6 Sep 2004 20:35:00 -0400 From: Joe Altman <fj@panix.com> To: freebsd-questions@freebsd.org Subject: Re: [another "me too"] Re: portindex/portindexdb Message-ID: <20040907003500.GA11100@panix.com> In-Reply-To: <413C0FAE.1000502@zonnet.nl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <format:bdb1_btree> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040907003500.GA11100>