ports/71558: using portupgrade results in ruby dumping core with bus error

Dru Lavigne dlavigne6 at sympatico.ca
Fri Sep 10 14:30:22 UTC 2004


>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 at 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:



More information about the freebsd-ports-bugs mailing list