Heap Information Doubt | developer.brewmp.com Heap Information Doubt | developer.brewmp.com

Developer

Heap Information Doubt

Forums:

Hi Experts,
I have run my application (BREW SDK2.1.3) in simulator using debugging. After I closed my application, the MS VC++ IDE gives the debugging information like bellow

Validating Heap...
------ Heap Info ------
255972 FREE
-------------------------
0 Alloc - Total
0 OEM
0 BREW
0 Apps
28 Wasted
255972 Free - Total
255972 Largest
0 Largest Non Seq.
0 Total Non Seq.
-------------------------

Can any one explain about above information.

Thanking you

hello thilsen,
Just look above that particular result in ur emulator 's output window there will be something called as ---------AppheapInfo-------, wherein it will display the pointers that cause memory leak .
Hope so this will help you.

hello thilsen,
Just look above that particular result in ur emulator 's output window there will be something called as ---------AppheapInfo-------, wherein it will display the pointers that cause memory leak .
Hope so this will help you.

Hi,
I can not found AppHeapInfo in emulator output window. And the heap details came when i debug from VC++ IDE. And ,this detail came after I closed the emulator.
Please help where i find AppHeapInfo detail

Hi,
I can not found AppHeapInfo in emulator output window. And the heap details came when i debug from VC++ IDE. And ,this detail came after I closed the emulator.
Please help where i find AppHeapInfo detail

Senthil,
I am not sure if you want to find memory leak or info about heapinfo.
The heapinfo is the one you have posted here. Also in addition if there are any leaks that can be detected by BREW, then you will see those lines allocated the memory. Also by seeing either OEM files/you app files name & nature of the call, you can identify the problem mostly.
I am not sure if there are any tools exist. Even IBM had real time s/w and which could not work with BREW as it uses multiple own mem allocs routines.
So easy way is to write a own malloc/realloc which should report you, then also watch for all routines which would allocate memory and you are responsible for release() of that.

Senthil,
I am not sure if you want to find memory leak or info about heapinfo.
The heapinfo is the one you have posted here. Also in addition if there are any leaks that can be detected by BREW, then you will see those lines allocated the memory. Also by seeing either OEM files/you app files name & nature of the call, you can identify the problem mostly.
I am not sure if there are any tools exist. Even IBM had real time s/w and which could not work with BREW as it uses multiple own mem allocs routines.
So easy way is to write a own malloc/realloc which should report you, then also watch for all routines which would allocate memory and you are responsible for release() of that.