Mark Karpeles wrote: > http://php.magicaltux.net/browse/ (lots of memleaks reported on 5.3 & > HEAD, seems to be glibc-related and not real memleaks, and this is not > up-to-date as I didn't run the tests for a while and didn't automate it > because it takes a lot of cpu)
Wondering why you did this. Was there something missing from our gcov valgrind output? http://gcov.php.net/viewer.php?version=PHP_5_3&func=valgrind And we have a per-extension code coverage thing here: http://gcov.php.net/PHP_5_3/lcov_html/ which seems like an interface we could tie this into. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
