VM Optimization Software
Shell The shell (target control in PB or VS) has a couple tools to quickly analyze device memory usage.
- "mi" quickly provides information about what processes are running in which slot. Vital statistics are also included like pages in use for code, data, and stack. Here is an example of "mi" output (Click to read this topic 4/24/2007 6:49:48 PM -BSPVMMIOutput).
- "mi kernel" dumps a brief listing of kernel data usage. Growth in the data line associated w/ HData can mean handle leaks. Growth in the data line associated with Crit/Evt/Sem/Mut can mean leaks in critical sections, events, semaphores, and mutexes. Here is an example of "mi kernel" output (Click to read this topic 4/24/2007 6:51:16 PM -BSPVMMIKernelOutput).
- "mi full" dumps a full listing of VM memory usage on a slot by slot basis. It is pretty good at telling you what area is in use by heaps, stacks, writable data, code segements, etc. Unfortunately it doesn't do a spectacularly good job associating the used space to specific DLLs. The tool "devHealth" lists all this information plus correlates it to DLL names. Here is an example of "mi full" output (Click to read this topic 4/24/2007 6:55:39 PM -BSPVMMIFullOutput).
No comments:
Post a Comment