Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46416 invoked from network); 3 Apr 2011 18:37:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Apr 2011 18:37:31 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:50201] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/C2-18667-76EB89D4 for ; Sun, 03 Apr 2011 14:37:28 -0400 Received: by fxm1 with SMTP id 1so3902798fxm.29 for ; Sun, 03 Apr 2011 11:37:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+7gtggnbE1SzeuBvtCx/YAFViSMayKWtg64LOuPYMxY=; b=X7H6SKWnQY7c0VjeVzRakvMF/qHmAWFhcFa2xP3c221lZItwOpMVNxPUXqgLebaPko s+0m5pL+gpY5oD2297zPDWcZirRfuj4e0xYpS8cugnUzd4n0oIHtzNi267wsSm36fA5Z Jr1/k620JyTd/ph8HVIoT9aoKOaYyl4DkWpl4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qf8r79GtvkSP8pBLj9eWdNmgrfuh9HEDw7uOj5yWqYTJuj8K4rPPWa9vIpXdSvtkI/ 9b1q2ot8w6+g9e/qjueX3DzhWUFyO0E4PzRdQlu+ct8yIPU7dYPHH2K9u4W1IJWuaa8S k9nAYDKilLE2MlWbN49aSQkQmwZdkzaEKoiVQ= MIME-Version: 1.0 Received: by 10.223.3.132 with SMTP id 4mr2316207fan.132.1301855845076; Sun, 03 Apr 2011 11:37:25 -0700 (PDT) Received: by 10.223.74.203 with HTTP; Sun, 3 Apr 2011 11:37:25 -0700 (PDT) In-Reply-To: <4D98A007.1060203@nouvo.com> References: <4D95B6AB.30608@templeet.org> <4D960169.3000400@templeet.org> <4D9849EA.9010805@nouvo.com> <4D985602.2080703@nouvo.com> <4D98A007.1060203@nouvo.com> Date: Sun, 3 Apr 2011 20:37:25 +0200 Message-ID: To: Pascal COURTOIS Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] how to find a memory corruption in php ? From: pierre.php@gmail.com (Pierre Joye) post it with the necessary steps to reproduce it. We may try to reduce the code to the minimal we need to get the leak (I remember someone having a tool for that) On Sun, Apr 3, 2011 at 6:27 PM, Pascal COURTOIS wrote: > Le 03/04/2011 15:46, Patrick ALLAERT a =E9crit : > >> Sounds like "now" is a good time to fill in a bug report at >> http://bugs.php.net/ :) > > =A0The trouble is I don't know how to fill in such bug report. > It happens with my template engine which is thousands of lines > of PHP. The template engine has been used since 2003 and the > bug appears with one single template which has nothing particular. > > =A0I guess if I make a bug report with all instructions to reproduce > the bug no one will ever look at it because it means installing > the framework. Ok, the installer does the job in 5 seconds but knowing > the number of open tickets in PHP, if I was a zend developper I'm > not sure I would look in priority in a bug which is hard to reproduce. :-= ( > > =A0What do you think ? > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org