[ruby18] bus error when updating portsdb

[Joshua Tinnin]

On Saturday 04 September 2004 07:54 pm, Chris <racerx at makeworld.com> 
wrote:
> Jason Harmening wrote:
> > I added a debug printf to portsdb.rb at line 586, and the bus error
> > always occurs at the entry for py23-bsddb3-4.2.4.  Don't know if
> > this means anything, but it may be useful.
> >
> >>Hi,
> >>
> >>I'm having the following problem whenever I run portsdb -Uu or
> >> portupgrade:
> >>
> >>Updating the portsdb <format:bdb1_btree> in /var/tmp ... - 11725
> >> port entries found
> >>.........1000.........2000.........3000.........4000.........5000..
> >>.......6
> >> 000.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8
> >>/portsdb.r b:587: [BUG] Bus Error
> >>ruby 1.8.2 (2004-07-29) [i386-freebsd5]
> >>
> >>Abort (core dumped)
> >>
> >>The bus error always occurs at exactly the same location (just past
> >> the 8000th entry) in the portsdb.  I run portsdb/portupgrade
> >> weekly and just began having this problem tonight.  System is
> >> 5.2.1-RELEASE-p9 i386.
>
> So - has thisbeen taken care of?

Some people have dealt with it in various ways, like deinstalling 
portmanager and portsman, forcing upgrade of all ports still dependent 
on ruby16 and deinstalling that, reinstalling ruby18 
( http://lantech.geekvenue.net/chucktips/jason/chuck/1079913751/index_html ), 
but none of that worked for me (though I didn't have ruby16 or any 
dependent ports). I've also tried removing /usr/ports and cvsup'ping 
again a couple times. I'm running 5.2.1-RELEASE-p9, though I've read of 
this occuring on 4.10 and 5.3 beta as well. For now I'm using 
portindexdb instead of portsdb -u, which is sort of a workaround.

- jt