Re: PHP 5.0.0 Test roll

Are you sure you don't have some stale build? I checked the same tests with valgrind and I get nothing. At 09:08 PM 7/13/2004 +0400, Antony Dovgal wrote:

On Tue, 13 Jul 2004 15:34:28 +0400 Antony Dovgal <tony2001@phpclub.net> wrote: Hi all! That's what valgrind says: 1) Zend/tests/bug26166.phpt Zend/zend_execute.c:1352 EX(Ts) = (temp_variable *) safe_emalloc(sizeof(temp_variable), op_array->T, 0); ==8511== 40 bytes in 1 blocks are still reachable in loss record 2 of

7==8511==    at 0x3C01E375: malloc (vg_replace_malloc.c:105)
==8511==    by 0x8222A55: _emalloc (zend_alloc.c:182)
==8511==    by 0x8222C77: _safe_emalloc (zend_alloc.c:238)
==8511==    by 0x8266E78: execute (zend_execute.c:1352)

2) Zend/tests/bug20240.phpt ==8478== 40 bytes in 1 blocks are still reachable in loss record 2 of

7==8478==    at 0x3C01E375: malloc (vg_replace_malloc.c:105)
==8478==    by 0x8222A55: _emalloc (zend_alloc.c:182)
==8478==    by 0x8231488: call_user_function (zend_execute_API.c:517)
==8478==    by 0x816D03B: user_shutdown_function_call

(basic_functions.c:2088) Dunno if it's the right thing to add if()'s around emalloc(), but with attached patch these warnings disappear, reducing valgrind logs in a half. --- WBR, Antony Dovgal aka tony2001 tony2001@phpclub.net || antony@dovgal.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php