On Tue, 19 Nov 2002, Marcus Börger wrote:
As far as i can tell from the source there is ZEND_TEST_EXCEPTIONS
to guard crash() but leak() isa allways there. Without debug leak() doesn't
report anything but it produces a leak.
hmm, you're right. I would vote to remove this function when not
At 14:04 20.11.2002, Derick Rethans wrote:
On Tue, 19 Nov 2002, Marcus Börger wrote:
As far as i can tell from the source there is ZEND_TEST_EXCEPTIONS
to guard crash() but leak() isa allways there. Without debug leak() doesn't
report anything but it produces a leak.
hmm, you're right. I
At 02:04 PM 11/20/2002 +0100, Derick Rethans wrote:
On Tue, 19 Nov 2002, Marcus Börger wrote:
As far as i can tell from the source there is ZEND_TEST_EXCEPTIONS
to guard crash() but leak() isa allways there. Without debug leak() doesn't
report anything but it produces a leak.
hmm, you're
On Wed, 20 Nov 2002, Andi Gutmans wrote:
At 02:04 PM 11/20/2002 +0100, Derick Rethans wrote:
On Tue, 19 Nov 2002, Marcus Börger wrote:
As far as i can tell from the source there is ZEND_TEST_EXCEPTIONS
to guard crash() but leak() isa allways there. Without debug leak() doesn't
report
As far as i can tell from the source there is ZEND_TEST_EXCEPTIONS
to guard crash() but leak() isa allways there. Without debug leak() doesn't
report anything but it produces a leak.
marcus
At 07:36 19.11.2002, Derick Rethans wrote:
On Tue, 19 Nov 2002, Marcus Börger wrote:
Shouldn't leak()
On Tue, 19 Nov 2002, Marcus Börger wrote:
Shouldn't leak() and crash() be disabled or without functionality
for normal use and instead have to be enabled with a configure
option?
--enable-debug is this switch AFAIK.
Derick
--
