Re: Segmentation fault when calling procs

> Explanation:
>
> The garbage collector was freeing the object A.new, even though a proc
> still existed with self = A.new.
>
> When you call the proc (block.call), it enters the proc fine, but it
> fails to call test() because its "self" is corrupted.

Ok that explains why we had no leakage in Ara's case of "leakage" with
the finalizers, that and
the fact that the finalizers have not been called of corse (see
http://rubyforge.org/tracker/index.php?func=detail&aid=17016&group_id=426&atid=1698
)

And the fact that you are allowed to do this also means that one has
to keep self in the binding of a proc.
I finally got it. Thanx
Robert

---
Whereof one cannot speak, thereof one must be silent.
Ludwig Wittgenstein