Just to answer the question about what Poser considers a memory leak (and to elaborate on Scott's answer to the question), Poser does intercept all calls to functions that allocate or free memory. When a chunk is allocated, Poser generates information on the context in which the allocation occurred, and "tags" the allocated chunk with that information. When the chunk is freed, Poser disposes of that context information. Finally, when the application quits, Poser walks the dynamic heap, looking for unfreed blocks owned by that application. When it finds any, it uses the tagged context information to generate a report.
-- -- Keith Rollin -- Palm OS Emulator engineer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
