From owner-freebsd-questions@FreeBSD.ORG Sat Sep 4 03:20:44 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A42A16A4CE for ; Sat, 4 Sep 2004 03:20:44 +0000 (GMT) Received: from lakermmtao01.cox.net (lakermmtao01.cox.net [68.230.240.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id E89B543D46 for ; Sat, 4 Sep 2004 03:20:43 +0000 (GMT) (envelope-from jlh@cox.net) Received: from [192.168.2.103] (really [68.13.124.67]) by lakermmtao01.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040904032042.DIGI17927.lakermmtao01.cox.net@[192.168.2.103]> for ; Fri, 3 Sep 2004 23:20:42 -0400 Message-ID: <41393693.2050908@cox.net> Date: Fri, 03 Sep 2004 22:29:23 -0500 From: Jeff Hinrichs User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD-Questions References: <89ceee704090210493f05add6@mail.gmail.com> <89ceee704090211342b63c20c@mail.gmail.com> In-Reply-To: <89ceee704090211342b63c20c@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: portupgrade, portsdb -U failing, ruby dumping core X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 03:20:44 -0000 Dan Finn wrote: > [ root @ stewie : /usr/ports/sysutils/portupgrade] : portupgrade ruby > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11725 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.1 (2004-05-02) [i386-freebsd5] > > Abort trap (core dumped) > > Any ideas what could be causing this? I recently installed portindex > and have been using that to generate indexes after reading someone > suggestion on one of the fbsd mailing lists. I don't think I have > made any other changes recently. I just sup'd and then portsversion produced this: [Updating the portsdb in /usr/ports ... - 11734 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.... where it is just sitting, so I pulled out top and see: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 21110 root 64 0 12540K 12068K RUN 10:53 99.02% 99.02% ruby18 Something is getting it stuck in a loop, it runs then explodes with the Bus Error. No gnome, no kde, this is on a 4.10 box that had been merrily running and sup'ing nightly. Hope someone figures this out.... Is their a debug switch for portsdb?? -Jeff