From: ts <decoux@...>
Date: 2003-10-29T20:34:51+09:00
Subject: Re: Win32OLE again

>>>>> "S" == Steve Tuckner <STUCKNER@MULTITECH.COM> writes:

S> Please anyone who has written C extensions or the author of Win32OLE,
S> let me know what is wrong with calling free on pointers allocated with
S> ALLOC_N.

 Well there is nothing wrong with calling free with ALLOC_N because like
 you've found ALLOC_N is just a call to malloc().

 But if it exist an error in the C extensions (bad memory management
 *elsewhere*) then the memory pool can be corrupted and this can explain
 the crash.

 Perhaps the error is in the extension Win32OLE (well, I don't know what
 do this extension and I've not looked at the source)


Guy Decoux