Re: Memory manager

I think sterling's looking for an OS X port. How is y!'s (inf)famous freebsd port of valgrind coming along? Rasmus Lerdorf wrote:

http://ozlabs.org/~paulus/valgrind-2.1.0-ppc.tar.bz2 On Mon, 5 Jul 2004, Sterling Hughes wrote:

yes!!! i currently don't have a 32 bit linux box available to me (i'm remote in ca for all of august), however, if someone gives me shell on one, i'll bang around on it with valgrind. -sterling On Mon, 5 Jul 2004 11:13:12 -0700 (Pacific Standard Time), Rasmus Lerdorf <rasmus@php.net> wrote:

I'd like to see a few people who know their way around Valgrind give this thing a workout before any release. I am planning on doing that as well this week, but the more codepaths tested, the better. -Rasmus On Mon, 5 Jul 2004, Andi Gutmans wrote:

Hi, Although I'm pretty sure I fixed the problem of the memory manager (in zend_alloc.c), I agree with Sterling that it's probably best to disable it for 5.0.0. I don't think that my fix will get enough testing until then for me to feel comfortable with including it. As I'd like to roll 5.0.0 by the end of the week, can developers please speak up if they have anything critical they are working on? Please also run latest head just to make sure that the malloc()/free() MM still works :) Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php