[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Re: SWIG / Ruby GC issues

M. Edward (Ed) Borasky

10/28/2007 5:22:00 AM

redroofgreentree wrote:
> Hi all,
>
> I have this really nasty SWIG/ruby GC issue. (Namely objects are being
> freed when I don't want them to be freed).
>
> These bugs are hard to track down, here's what would really help me:
>
> Is there some way I can tell ruby that when it frees an object, to ZERO
> out that entire region in memory? It'll make tracking down the bug so much
> easier.
>
> Thanks!
>

Well ... I guess I would start off by saying, "gdb is your friend". :)
But all SWIG does is generate wrapper/interface code between the Ruby
and the C or C++ code. Can you make this work without SWIG?
1 Answer

Alex Fenton

10/28/2007 3:03:00 PM

0

M. Edward (Ed) Borasky wrote:
> redroofgreentree wrote:
>> I have this really nasty SWIG/ruby GC issue. (Namely objects are being
>> freed when I don't want them to be freed).
>>
>
> Well ... I guess I would start off by saying, "gdb is your friend". :)
> But all SWIG does is generate wrapper/interface code between the Ruby
> and the C or C++ code. Can you make this work without SWIG?

SWIG does help with memory management,; there's an unusually helpful
section on GC in the SWIG docs, which repays close reading
http://www.swig.org/Doc1.3/Ruby.html...

You definitely need a debugger to identify what's getting prematurely
destroyed, but once you have a stack trace which shows what method is
being called on a deleted object, it's normally not hard to write a
%markfunc to protect it

alex