Date: Fri, 10 Sep 2004 14:27:34 GMT From: Dru Lavigne <dlavigne6@sympatico.ca> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/71558: using portupgrade results in ruby dumping core with bus error Message-ID: <200409101427.i8AERYtw074055@www.freebsd.org> Resent-Message-ID: <200409101430.i8AEULIm077804@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 71558 >Category: ports >Synopsis: using portupgrade results in ruby dumping core with bus error >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 10 14:30:21 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Dru Lavigne >Release: 5.2-RELEASE >Organization: >Environment: FreeBSD dru.domain.org 5.2-RELEASE FreeBSD 5.2-RELEASE #0: Sat Jun 5 09:54:55 EDT 2004 root@dru.domain.org:/usr/obj/usr/src/sys/NEW i386 >Description: Problem started Sept. 5 when a scripted upgrade check hung at "portversion -l "<"". Top showed 3 ruby18 processes tying up about 99% CPU. All ruby and portupgrade were deinstalled from system and reinstalled several times over a few days with same results. Running portupgrade results in: /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) (ruby18), uid0: exited on signal 6 (core dumped) >How-To-Repeat: Run portupgrade, portversion or portsdb on affected system. portsclean runs just fine. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409101427.i8AERYtw074055>