From owner-freebsd-ruby@FreeBSD.ORG Thu Feb 12 17:06:09 2009 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 236EF1065675 for ; Thu, 12 Feb 2009 17:06:09 +0000 (UTC) (envelope-from saad@hush.com) Received: from smtp12.hushmail.com (smtp12.hushmail.com [65.39.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 0A6958FC14 for ; Thu, 12 Feb 2009 17:06:08 +0000 (UTC) (envelope-from saad@hush.com) Received: from smtp12.hushmail.com (localhost.localdomain [127.0.0.1]) by smtp12.hushmail.com (Postfix) with SMTP id 619257004F for ; Thu, 12 Feb 2009 16:33:54 +0000 (UTC) Received: from smtp.hushmail.com (app1.hushmail.com [65.39.178.74]) by smtp12.hushmail.com (Postfix) with ESMTP for ; Thu, 12 Feb 2009 16:33:53 +0000 (UTC) Message-ID: From: Saad Kadhi To: FreeBSD Ruby Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 12 Feb 2009 17:33:51 +0100 X-Mailer: Apple Mail (2.930.3) Subject: ruby 1.8.6 patchlevel 287 dumps core on 7.0-RELEASE-p7 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 17:06:09 -0000 Hi, I am using Ruby 1.8.6 (2008-08-11 patchlevel 287) on FreeBSD 7.0- RELEASE-p7. I have some code that -among other things- parses XML files and when it does in at least one case, it dumps core with the following error msg: -x-x-x- /usr/local/lib/ruby/1.8/rexml/parent.rb:19: [BUG] object allocation during garbage collection phase ruby 1.8.6 (2008-08-11) [i386-freebsd7] -x-x-x- At times, I get a different error msg: -x-x-x- /usr/local/lib/ruby/1.8/rexml/namespace.rb:16: [BUG] object allocation during garbage collection phase ruby 1.8.6 (2008-08-11) [i386-freebsd7] -x-x-x- I initially developed my code using Ruby 1.8.6 patchlevel 111 on the same platform and everything worked as expected. And when I upgraded to the latest stable version from ports, I started having these issues. Staying with 1.8.6 patchlevel 111 is not an option since this version is riddled with security vulnerabilities. Any ideas on how to fix this problem? TIA. -- Saad Kadhi "It might look like I'm standing motionless, but I'm actively waiting for my problems to go away." Bob the Dinosaur, Dilbert.