On Thu, 23 Jun 2005, Zeev Suraski wrote:
> At 03:17 23/06/2005, Marcus Boerger wrote:
> >Hello Zeev,
> >
> > thanks for clarifying. Any chance we could change that for
> >"normal/unproblemeatic" exit()s in the future with run-tests
> >in mind?
>
> The trick would be how we can detect a non proble
At 03:17 23/06/2005, Marcus Boerger wrote:
Hello Zeev,
thanks for clarifying. Any chance we could change that for
"normal/unproblemeatic" exit()s in the future with run-tests
in mind?
The trick would be how we can detect a non problematic exit(). For example,
function foo() { exit(); }
fun
Hello Zeev,
thanks for clarifying. Any chance we could change that for
"normal/unproblemeatic" exit()s in the future with run-tests
in mind?
marcus
Wednesday, June 22, 2005, 4:03:35 PM, you wrote:
> When exit() is called, like any other case in which zend_bailout() is used,
> there can be memo
When exit() is called, like any other case in which zend_bailout() is used,
there can be memory blocks which will not be 'properly' freed, and we have
to rely on the memory manager to free it. So the fact leaks are not shown
in case of exit() is intentional.
Zeev
At 05:19 20/06/2005, Marcus
Hello internals,
i just stumbled over a strange issue while testing. Some of my tests
have exit(0) at the end for easier test verification. Now i found a new
one that has a few memleaks but only reports them if i drop that exit(0)
line. Is this something we need to fix (e.g. exit() omits leakage
