I have an intermittent bug that causes the Palm to reset, I haven't any hard evidence yet but I have a strong feeling that it's happening inside MemHeapCompact. Before, it was only happening when exiting the program but now it has started happening when opening a settings dialog. And it started happening right after I added a MemHeapCompact call in that dialog.

My questing is: Is there some kind of tool that can search through the memory heap (the dynamic one) and detect what has gone wrong? It might at least show which allocation that was corrupted.

I tried making a sort of "purify"-wrapper around MemPtrNew. It was possible to add some buffer space after the allocation and check it when returned, but when I tried adding space before the allocation and return a pointer some bytes into the chunk, something broke.

I've also tried the simulator but I don't seem to be getting the same crash there.

Is there some other way to find out what's happening?

Magnus


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

Reply via email to