Re: [Fxruby-users] Core dump when exiting

[Chris M. <ze...@gm...>]

Hi!

On Mon, Jan 05, 2004 at 10:59:42PM -0800, Joel VanderWerf wrote:

> >Using ruby 1.8.{0,1}, fox-1.0.{43,48}, FXRuby-1.0.{25,27} on 
> >Linux/Intel and Solaris/Intel and WindowsXP:
> >
> >I have a FOX application, everything works fine. But as soon as
> >I call 'exit' from within (or send a FXApp::ID_QUIT to getApp())
> >I get something like:
> >
> >------------------------------------------------
> >./rootwindow.rb:133: [BUG] Segmentation fault
> >ruby 1.8.1 (2003-12-25) [i686-linux-gnu]
> >
> >Aborted
> >------------------------------------------------
> >
> >Since this is not a very expressive error message: 
> >
> >Is this behaviour known to anyone? Any hints in which direction
> >I should go finding this error?
> 
> What I always try first in these situations is: turn off garbage 
> collection with GC.disable. If that stops the segfault, then it's a good 
> bet there's a bug somewhere in the mark/free funcs within FXRuby.

Ok, tried that, no change.

> Other than that, I would try paring down the app to the minimal code 
> that will reliably cause the problem, and then post it here. Of course, 
> that can be hard work....

So far I just can say this:

I use the method 

FXTreeItem *addItemLast(FXTreeItem *p, FXTreeItem *item, ...)

to insert an (from FXTableItem derived) item into an FXTreeList.

When i use

FXTreeItem *addItemLast(FXTreeItem *p, const FXString &text, ...)

it works just fine.

As soon as I find some spare time I'll try to break this down into
a smaller example.

Anyway, thanks for your answer!
-- 
chris