I appreciate POSE usefullness in detecting memory leaks. Nevertheless, detecting source line also has its value. But allow me one question: Is there some mechanism checking for writes past allocated buffer?
Jan Slodicka ----- Original Message ----- From: "Keith Rollin" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Monday, January 20, 2003 11:44 PM Subject: Re: Memory Leak tracking? > At 11:35 PM +0100 1/20/03, Jan Slodicka wrote: > >I repeat what was said in this forum within a few last days: > > > >Look at the threads "POSE reports memory leak even when I don't allocate" > >and "Memory leaks". > > > >Read http://www.fifthgate.org/articles/palm_mem_leaks.html > > And I'll repeat what I said before: this article is out of date, at > least with respect to Poser's facilities. Poser for the last couple > of years has been able to report memory leaks at the function level > (that is, it identifies what functions caused the leak). Other > techniques (like the one described in the article or the one you > included (and that I snipped)) can report leaks at the source code > line level. However, also keep in mind that Poser's report shows the > stack crawl, so that if Function A leaks memory, you know the context > in which Function A was called. It also doesn't require modifying > all of your call sites, and doesn't add any overhead. > > I've contacted the author of the above cited article; hopefully he'll > update it. > > -- Keith Rollin > -- Palm OS Emulator engineer > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
