Brian,
You've done this and it works? It seems to me that it wouldn't. My understanding
is that the simulator allocates a big block of memory at startup and turns it
into a native Palm heap. The "leaks" dcmd would know about the big block, but it
wouldn't know about the Palm OS memory manager data structures within it.
-- Keith Rollin
-- Palm OS Emulator engineer
Brian Hall <[EMAIL PROTECTED]> on 07/29/99 05:02:02 AM
Please respond to [EMAIL PROTECTED]
Sent by: Brian Hall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: Re: Finding a leak
>I've got a memory leak in a routine that dynamically sets up the string for
>a popup list. The thing is, it takes 22 or 23 runs through the routine to
>produce a crash, and I can't find the leak by hand.
>
>Does anyone have any pointers (no pun intended) on how to track the sucker
>down?
If you are developing on a Mac, try the "leaks" Macsbug dcmd with a
simulator build of your app.
Brian
_____________________________________________________________________
Mark/Space Softworks voice 408-293-7299
111 West Saint John, 3rd Floor fax 408-293-7298
San Jose, CA 95113 <http://www.markspace.com>
Mac OS, PalmOS, Windows, Web and Newton Software & Solutions:
PageNOW!, PageME!, PhoneWatcher, Online, Communicate,
ZMODEM, Telnet, PC-ANSI, Videotex CTB Tools
