----- Original Message ----- From: "Joe Altman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 7:35 PM Subject: Re: [another "me too"] Re: portindex/portindexdb
> 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. No, it's not hardware...... I've fixed mine following the earlier threads. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
