Memory leaks from Purifier

[Ship1]

Hi,
How do i debug the memory leaks given below which I get using the
Rationals Purifier for a C++ code.

[i] Summary of all memory leaks... {121604 bytes, 7 blocks}
[W] MLK: Memory leak of 65536 bytes from 2 blocks allocated in
BinDataPrep.exe
Distribution of leaked blocks
Allocation location
VirtualAlloc [KERNEL32.dll]
??? [BinDataPrep.exe ip=0x004125e3]
??? [BinDataPrep.exe ip=0x004122b2]
??? [BinDataPrep.exe ip=0x0041177e]
??? [BinDataPrep.exe ip=0x00427059]
[W] MLK: Memory leak of 32768 bytes from 1 block allocated in
BinDataPrep.exe
Distribution of leaked blocks
Allocation location
??? [BinDataPrep.exe ip=0x00427059]
[W] MLK: Memory leak of 16836 bytes from 1 block allocated in
BinDataPrep.exe
[W] MLK: Memory leak of 4096 bytes from 1 block allocated in
BinDataPrep.exe

[Larry Brasfield]

"Ship1" <sh************ *@gmail.com> wrote in message news:39******** *************** ***@posting.goo gle.com...

Hi,
How do i debug the memory leaks given below which I get using the
Rationals Purifier for a C++ code.

[ Cut Purify blat showing allocation IP for leaked blocks.]

Cause your build to generate a map. The map can
be used to assign each instruction pointer (aka 'IP')
value to a particular function. With your program
in the debugger, in 'view assembly' mode, go to the
offending function and find out which statement best
corresponds to the exact IP value. Then, somehow,
(preferably with a review of your design approach
and understanding of memory management issues),
decide why each of those allocations results in no
corresponding release of the allocated memory.
You will, in effect, need a free or delete for each
malloc or new executed in your code. This may
mean correction of a destructor or an operator=
implementation.

--
--Larry Brasfield
email: do************* **********@hotm ail.com
Above views may belong only to me.