Re: Is there any easy way to find the cause of a memory leak

2005-11-11 Thread Michal Seliga
in project settings switch off optimalizations and inlines, and switch on 'generate a6 stack frames' and 'generate macsbug debug symbols' with this you will have much better possibilities to debug cp wrote: > Hi Logan, > > >>Build a version of your app with debug symbols > > > How to do that

Re: Is there any easy way to find the cause of a memory leak

2005-11-11 Thread cp
Hi Logan, > Build a version of your app with debug symbols How to do that in codewarrior ? --cp -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/

Re: Is there any easy way to find the cause of a memory leak

2005-06-06 Thread Logan Shaw
Salvador Buendia wrote: I'm using CodeWarrior 9 and PalmOs Emulator and when I exit my program the emulator warn me of a memory leak. I used to solve this commenting functions or reading my code but I never understood well what was the information that the emulator was giving me about the memory

re: Is there any easy way to find the cause of a memory leak

2005-06-06 Thread roderick young
Your classical approach is good, to read your code and comment out portions to narrow down the failure. That's what I would do first. However, failing that, I might try printing out a line to a log file every time I allocated memory, giving the address, and every time I freed memory, again giv