From: Steve Tuckner <STUCKNER@...>
Date: 2003-10-29T08:05:56+09:00
Subject: Win32OLE again



I am having trouble trying to figure out what is wrong with the Win32ole
extension when running on 1.8.0.  I have narrowed it down to the calling
of 
 
ALLOC_N and freeing what is returned from there.
 
If I just call malloc and free that pointer, that works OK.
 
I looked at some other ruby extensions and they don't call ALLOC_N.
 
I looked at the ruby source and it seems that ALLOC_N is just a call to
ruby_malloc which in turn calls malloc. So I should be able to free it
just fine. 
 
Please anyone who has written C extensions or the author of Win32OLE,
let me know what is wrong with calling free on pointers allocated with
ALLOC_N.
 
Thanks in advance,

Steve Tuckner