A chunk underlocked error usually indicates that you are calling
MemHandleUnlock more times than you've called MemHandleLock for a particular
chunk. Usually this occurs because you've carefully Unlocked the chunk in a
block of code and then somewhere else (cleanup portion of the same function,
or in the calling function) you try to unlock it again.
-----Original Message-----
From: Chad Harrison [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 11:25 PM
To: Palm Developer Forum
Subject: Re: What's a good way to debug memory leaks?
if you are getting an underlock chunk, I think it means that you are
trying to free up a non existant pointer, i.e., one that doesnt exist or
has already been been freed.
besides using the dump and console, you could first make sure that your
code isnt trying to free something that isnt there...
On Sat, 3 Feb 2001, DIAMOND JEFF wrote:
> Serves me right - I've used nothing dynamic so far but databases, and
> sure enough, my code was robust.
>
> Now I broke down and finally used MemPtrNew and MemPtrFree, and I have a
> memory leak (underlocked chunk).
>
> I'm using Codewarrior 7 under Windows. Can anyone recommend a good way
> to find a memory leak?
>
> I tried using the Palm Debug Console, but to be honest, I can't make
> much sense out of the heap dump.
>
> And direction is appreciated.
>
> Thanks!
> - Jeff
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
