> If your C/C++ object has a VALUE member, you need only register the
> address of that just once, and unregister it in the destructor.  As long
> as your C/C++ object is around, the VALUE is registered and the object
> it is tied to will not go away.

That is exactly what I am doing I just wanted to spell out the scenario as
it may happen when there are more than one C++ wrapped reference to a ruby
object.

I'll try that volatile thing and see if it makes a difference.

Cheers,

Thomas