Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18782 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4182 invoked by uid 1010); 11 Sep 2005 22:54:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 4166 invoked from network); 11 Sep 2005 22:54:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2005 22:54:59 -0000 X-Host-Fingerprint: 64.233.184.195 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.195:26915] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 52/86-27924-2C5B4234 for ; Sun, 11 Sep 2005 18:54:59 -0400 Received: by wproxy.gmail.com with SMTP id 36so2118802wra for ; Sun, 11 Sep 2005 15:54:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OC3mQTbuynbrSJ9w083bKhioPJjehbH9mo34xdEwWtBG/XB4NBSxA7otMGCnHcOjzfUXYnrQGdMA5rUDjfLudQs8Vuxn2e4nxaGkddyMYZTQia58ly932YQ70/3W2PmMSuByNJyZ4rSLHeleLL6Xk3FVVUUzAhFvU/3ytptqHvc= Received: by 10.54.27.71 with SMTP id a71mr2116530wra; Sun, 11 Sep 2005 15:54:55 -0700 (PDT) Received: by 10.54.154.16 with HTTP; Sun, 11 Sep 2005 15:54:55 -0700 (PDT) Message-ID: Date: Mon, 12 Sep 2005 00:54:55 +0200 Reply-To: pierre.php@gmail.com To: internals@lists.php.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: 5.0.5, BC break, fatal error From: pierre.php@gmail.com (Pierre Joye) Hello, Without arguing again about the """fix""" for the memory corruption discovered earlier this summer and without anyone able to reproduce with a medium size script, _why_ in the world one applies this fix to the 5.0 branche? 5.0.5 was supposed to be a _security_ fix release only. I do know many people who will upgrade and they do have tousands of lines of codes wrote by many people. Do you really think the answers given in the various bug reports (http://bugs.php.net/bug.php?id=3D34468) is good? And please, do not tell me to come with a patch to fix this problem, the fix should have not been applied to 5.0.5, period. Any chance to roll it again without the fix? The fix is not listed in the NEWS neither in the Changelog. I know that the chance to get that fixed is null, but I would like to hear some valid explanations besides the common arrogant answers. Regards, --Pierre