I just found the problem. Actually it concerned the debug build only (I did not know about it): Here we redirect memory allocations (MemPtrNew and MemHandleNew) to do some bookkeeping. After that we called MemChunkNew, but passed bad ownerId. By inspecting Emulator sources I found that they inspect only the blocks with the app ownerId, so our leaks were ignored.
As far your problem is concerned: If you get the dialog announcing leaks, then identical code does logging (Emulator file EmPatchModuleMemMgr.cpp); there is just one change: instead of counting a log function is called. Probably you have switched off warnings in Emulator/Menu/Settings/Logging. Jan ----- Original Message ----- From: "Matt Graham" <[EMAIL PROTECTED]> Newsgroups: palm-dev-forum To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Thursday, September 04, 2003 8:50 PM Subject: Re: Emulator not detecting memory leaks > > "Jan Slodicka" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > > Meanwhile I returned to sysAppLaunchCmdNormalLaunch. New emulator session > > did not help. Neither emulator restart. > > > > This doesn't sound like the problem you're having, but I figure I'll say it > anyway. > It seems like if I start POSE by running or debugging my app in codewarrior, > I get the box telling me I have memory leaks, but then nothing gets written > to the log file. > > matt > > > > -- > 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/
