Reply to thread

Message: [QUOTE="Erik Lindblad, post: 4648659"] Hmmm, getting very close now. The idea to wrap SomeOpaqueStruct worked like a charm. Now I can allocate, initialize and retreive the DATA through this wrapped construction. So many thanks for that one. However there is one problem left. All the stuff above is only possible within the wrapper C code. Once the library call exits and I am back in Ruby land, the wrapped struct (SomeOpaqueStruct in your example) is freed and I get a segmentation fault. I realize this is because of how the wrapped library works but do you know of any way to prevent this or how to copy the struct, thereby saving it for the afterworld? Regards Erik [/QUOTE]