Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10917 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63100 invoked by uid 1010); 5 Jul 2004 19:32:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 63049 invoked from network); 5 Jul 2004 19:32:03 -0000 Received: from unknown (HELO colo.lerdorf.com) (66.198.51.121) by pb1.pair.com with SMTP; 5 Jul 2004 19:32:03 -0000 Received: from DELL (c-24-6-1-90.client.comcast.net [24.6.1.90]) by colo.lerdorf.com (8.12.11/8.12.11/Debian-5) with ESMTP id i65JVvtx008289; Mon, 5 Jul 2004 12:31:58 -0700 Date: Mon, 5 Jul 2004 12:34:17 -0700 (Pacific Standard Time) To: sterling@apache.org cc: internals@lists.php.net In-Reply-To: <24e5f3b704070512011a9e3ba0@mail.gmail.com> Message-ID: References: <5.1.0.14.2.20040705100648.0203b2f0@127.0.0.1> <24e5f3b704070512011a9e3ba0@mail.gmail.com> X-X-Sender: rasmus@lerdorf.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on colo Subject: Re: [PHP-DEV] Memory manager From: rasmus@php.net (Rasmus Lerdorf) 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 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 >