When tracking the memory leaks in my application I end up with several
functions where I use the following method to access data:

MemHandle h;
MemPtr p;
[... attach h to a record ...]
p = MemHandleLock (h);
error = DmWrite(p, settings_off_currentEssID, &info, sizeof(Int32));
MemHandleUnlock(h);

>From theese funcions I get a memory-leak problem.
I have tried to add a MemPtrUnlock call but that causes the application to
crash due to free handle. Should I use some other function or do something 
else entirely?

(I am using closeAllForms and also return false from each forms handler for
the formclose event, and I'm using the -mdebug-labels option when compiling).

Veronica

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to