|
From: Tom H. <th...@cy...> - 2004-07-12 17:29:31
|
In message <7FD...@az...>
Maretick Scott-SMARETI1 <SMA...@mo...> wrote:
> So when I see this output, how can I determine where the leaks are at in
> the code?
By reading the stack trace for the leak to see where the leaked
memory was allocated and then examining your code to see why it
isn't being freed again.
> Obviously, there's a problem in
> /vob/mm2/plat/src/libMMUnsorted/api_HashTable.c on line 118?
That's what it says, yes.
> What about in the "LEAK SUMMARY"
What about it? It's a sumary of the total amount of memory leaked.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|