>I'm also having trouble with memory leaks. My app is leaking 660 bytes
>every time it's run. I've used "hd 0" to find the blocks and their
>sizes. So far that info hasn't been enough for me to track down the
>problem though. What's the next step I should take?
If you're allocating structures dynamically, why not put some sort of
readily recognizable flag or code bytes in the first or last few
bytes so that you can figure out where you're making the allocation
when looking at the heap dump?
Or, every time you allocate a block, write a debug message to the
debugger console using DbgMessage? Or, write some information to a
database or a memo or to......?
There are probably also one or more knowledge base articles and there
are definitely mailing list archive messages that discuss this topic.
Regards,
Steve Mann
--
-------------------------------------------
Creative Digital Publishing Inc.
1315 Palm Street, San Luis Obispo, CA 93401-3117
-------------------------------------------
805.784.9461 805.784.9462 (fax)
[EMAIL PROTECTED] http://www.cdpubs.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
