Local Heap problem in WLE client

Question

Hi all,
In visual c++ client, I've a local object which is pass to WLE server.
The server will return the value to this local object. However, the local
object is therefore pointing to the memory address of server's output
object . So, in vc++ client, when program try to free memory of local
object. "Debug Assertion Failure" meesage is occur. _CtrlHeapPointerHeap is
always fail for this local object. And my program is dead.
Do U know how to solve this problem?
Thanks!
Sam

Answer 1

In general, the memory for in-out parameters needs to be allocated
dynamically. The caller (i.e., your code) is responsible for allocating and
initializing the memory before passing the parameter. When the call returns,
the WLE library will de-allocate your memory and allocate memory for the object
being returned and change the pointer passed in to refer to that newly
allocated memory. Your code only needs to de-allocate what is in that pointer
once the call returns (and you are finished with the object); you should not
worry about the previously allocated memory as the WLE libraries have already
freed that for you (in accordance with the CORBA specification).
Hope this helps,
Robert
Sam Ho wrote:
Hi all,
In visual c++ client, I've a local object which is pass to WLE server.
The server will return the value to this local object. However, the local
object is therefore pointing to the memory address of server's output
object . So, in vc++ client, when program try to free memory of local
object. "Debug Assertion Failure" meesage is occur. _CtrlHeapPointerHeap is
always fail for this local object. And my program is dead.
Do U know how to solve this problem?
Thanks!
Sam