From: Joel VanderWerf <vjoel@...>
Date: 2007-12-10T10:57:50+09:00
Subject: Re: FXRuby Segmentation fault

Ernst Tanaka wrote:
> Thanks Axel for your reply.
> 
> Still working on the errors.
> 
> I am also getting;
> 
> This application has requested the Runtime to terminate it in an unusual 
> way.
> Please contact the application's support team for more information.
>> Exit code: -1073741819
> 
> 
> I have proof that the error reproduces itself  on a non-consistent 
> bases.
> 
> - One time program runs perfectly.
> -  make non essential change; like I add a line x = " "
> - next time program does not run and gives the above mentioned errors.
> - remove of line --> still errors
> 

Symptoms like this sometimes mean there is a memory management problem 
(possibly somewhere in fxruby). It might mean that an object is being 
freed even though there is a reference to it. Try doing this somewhere 
early in your program:

   GC.disable

If you do that, the program will consume increasing amounts of memory, 
so it is not a solution to the problem. But if the crash does not 
happen, then that probably indicates a memory management bug of some kind.

The source of the problem may be hard to find. You can insert GC.start 
after creating objects (remove the GC.disable first). This may help 
determine which allocation is the culprit. (Someone suggested a ruby 
option to tell GC to collect frequently, which would help, but AFAIK 
this doesn't exist yet.)

Also, you can try to cut your program down to the smallest example in 
which the bug still happens.

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407