Thanks a lot. the problem has been solved!!
Good to hear that. But did you realise how Ben was able to tell where
exactly lies the problem ? :-) If you understand that, you would be
able to solve the leaks wihtout any difficulties in furutre. Its
related to name mangling concept in C++. C++
: WARNING:
0.000:
Non-relocatable chunk leaked at 0x0003C460, size = 8 0.000: Chunk
allocated by:
0.000: Unknown @ 0x000474D0
0.000: Unknown @ 0x00046F08
0.000: Unknown @ 0x0004732A
0.000: PrvSendEventToForm
0.000: FrmDispatchEvent
From the size of the log file, it looks the leaks come from the
link-list. The log file contains the following sentence:
Non-relocatable chunk leaked at 0x0003C460, size = 24
Looks like you allocated the memory by MemPtrNew() [ or new if
C++ ] and then forgot to de-allocate it.
Would
:
0.000: WARNING: Begin Memory Leak Dump
0.000: WARNING:
0.000: Non-relocatable chunk leaked at 0x0003C460, size = 8
0.000: Chunk allocated by:
0.000: addMember__10PlayerListFP6member
0.000: PlayersListFormRevMsg__Fv
0.000
Thanks a lot. the problem has been solved!!
Ben Combee [EMAIL PROTECTED] ??:[EMAIL PROTECTED]
At 02:25 PM 8/14/2003, gamepower111 wrote:
I have changed the setting, and now the dump from the log file looks
like:
(but I still dont know how to solve the problem:
This is saying that the
At 02:25 PM 8/14/2003, gamepower111 wrote:
I have changed the setting, and now the dump from the log file looks like:
(but I still dont know how to solve the problem:
This is saying that the memory that wasn't freed was allocated from your
PlayerList::addMember method, from your
From the size of the log file, it looks the leaks come from the
link-list. The log file contains the following sentence:
Non-relocatable chunk leaked at 0x0003C460, size = 24
Looks like you allocated the memory by MemPtrNew() [ or new if
C++ ] and then forgot to de-allocate it.
Would you
Hi all,
I have created a link-list during running, and I have implemented a
desconstractor for it. When I exit the palm os application, memory leak
occurs. From the size of the log file, it looks the leaks come from the
link-list. The log file contains the following sentence:
Non-relocatable
