[fxruby-users] FXTableItem.new segmentation fault

Tim Smith tsmith at tektone.net
Thu Sep 25 16:50:36 EDT 2008

The SWIG issue may indeed affect only versions of Ruby from 1.8.7 and
1.8.6 patchlevel 117 onward.  I only saw the "object allocation during
garbage collection phase" message on Ruby 1.8.7.  However, the
FXTableItem.new crash predates those versions.  The backtrace I posted
was from ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-linux].  And I
have just now reproduced the crash on ruby 1.8.2 (2004-12-25)

As I observed in my last message, it looks like this crash happens when
garbage collection triggers a call to getIcon() during the
initialization of an FXTableItem, before the item is fully inserted into
FXRuby_Objects.  This problem goes back to at least Ruby 1.8.2 and
FXRuby 1.6.14.
Tim Smith

-----Original Message-----
From: fxruby-users-bounces at rubyforge.org
[mailto:fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson
Sent: Thursday, September 25, 2008 2:48 PM
To: fxruby-users at rubyforge.org
Subject: Re: [fxruby-users] FXTableItem.new segmentation fault

On Thu, Sep 25, 2008 at 1:00 PM, Melton, Ryan <rmelton at ball.com> wrote:

> FXRuby does not work with Ruby 1.8.7 due to a bug in SWIG.
> Unfortunately the same ruby change that results in the "object
> during garbage collection phase" made it into the Ruby 1.8.6 releases
> well at around version 117.  So to use FXRuby, you must use a version
> Ruby 1.8.6 that is before r117.

I didn't realize that this "fix" also made it into Ruby 1.8.6.

> Yes, this sucks.  Hopefully SWIG will be fixed soon, or Lyle will work
> around the issue like the wxRuby group did.

I'll see what I can do.
fxruby-users mailing list
fxruby-users at rubyforge.org

More information about the fxruby-users mailing list