Re: Memory leak when internal pointer passed out as parameter
- From: "Mike" <mail2mz@xxxxxxxxx>
- Date: 3 Apr 2007 11:52:30 -0700
On Apr 3, 2:29 pm, rober...@xxxxxxxxxxxxxxxxxx (Walter Roberson)
wrote:
In article <1175623345.081280.166...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Mike <mail...@xxxxxxxxx> wrote:
I have following existing code. And there is memory leak. Anyone know
how to get ride of it?
Are you certain that it is a memory leak, and not a memory
fragmentation problem?
--
All is vanity. -- Ecclesiastes
Rational Purify checked the code, and reported memory leak on foo1
when we allocate memory. I assum e that the compiler will allocate a
new block of memory when foo1 returns. Then the memory allocated
within foo1 will remain in the system heap forever. However I have no
way to verify it.
.
- Follow-Ups:
- Re: Memory leak when internal pointer passed out as parameter
- From: Daniel Rudy
- Re: Memory leak when internal pointer passed out as parameter
- From: Keith Thompson
- Re: Memory leak when internal pointer passed out as parameter
- From: Ben Pfaff
- Re: Memory leak when internal pointer passed out as parameter
- From: Flash Gordon
- Re: Memory leak when internal pointer passed out as parameter
- From: Walter Roberson
- Re: Memory leak when internal pointer passed out as parameter
- References:
- Memory leak when internal pointer passed out as parameter
- From: Mike
- Re: Memory leak when internal pointer passed out as parameter
- From: Walter Roberson
- Memory leak when internal pointer passed out as parameter
- Prev by Date: Re: Header questions
- Next by Date: Re: Memory leak when internal pointer passed out as parameter
- Previous by thread: Re: Memory leak when internal pointer passed out as parameter
- Next by thread: Re: Memory leak when internal pointer passed out as parameter
- Index(es):
Relevant Pages
|