> The only problem I have with it is that it does not > give line numbers.
Before we had memory leak detection built into Poser, many people wrote their own memory leak detection systems. I wrote two myself. The first one used macros to intercept calls to MemPtrNew, etc. By using the __LINE__ and __FILE__ macros, I could pinpoint the line number where the allocation occurred. But I didn't get the entire stack, so utility functions that did allocations caused problems. The other problem with this approach is that you're only intercepting allocations made directly by your application. My second leak detector patched traps instead, just as Poser does now. I found this approach worked better most of the time. -- Danny @ PalmSource -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
