Re: [Fxruby-users] bug: descending FXTreeItem causes coredump?

[Kevin B. <kev...@sy...>]

Joel,

Thanks for the response.  Definitely sounds like the same problem. 
Possible reason that Ctrl-Q and File->Quit act differently: the tree no
longer has the focus.  It ONLY happens when the tree has the focus and a
subitem is selected.

FWIW, I also have developed a Ruby extension (for commerical use).  I
believe there is some kind of bug in Ruby 1.8's cleanup that causes an
infinite loop whenever you try to use rb_io_write (via rb_warn, etc.)
when ruby_finalize_0 has been called, which FXRuby also encounters after
the bad call to SetFocus.  I haven't been able to isolate that, but, it
sure does make finding the actual cause of the MY (and FXRuby's problem)
more difficult.  I ran into this problem because memory was being
trashed (because I was not forcing my objects to clean up orderly, no
matter what object the GC cleaned up first.)

Kevin

On Mon, 2003-09-29 at 16:27, Joel VanderWerf wrote:
> Joel VanderWerf wrote:
> 
> > I think that's the same bug that I reported here about a month ago, but 
> > couldn't isolate very well. Attached is Lyle's response.
> 
> Well, now it is :)
> 
> ______________________________________________________________________