it still crashes even with GC.disable
therefore verifying that it isn't garbage collection causing the problem
thanks for the response :)

On Dec 28, 2004, at 11:04 AM, ts wrote:

>>>>>> "A" == Alexander Kellett <ruby-lists / lypanov.net> writes:
>
> A> i'm right in saying that i haven't messed up
> A> with gc if when i call GC.disable it still fails right?
> A> (i'd made that assumption, but was not sure if it was correct)
>
>  Well, in this case if you call GC.disable it must work. But this is 
> not a
>  good idea because the memory will grow and ruby will be slower.
>
>  Generally there is always a better way to do than use GC.disable.
>
>
> Guy Decoux