Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51789
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
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;
        b=N8h0+049r+yWYtZEmiBlb7b2DJ+FaCGF4IFTohKczAZMGIFtxgdqKa5ZlXYclt6m2X
         m1wVTOVanYQ/yV6R1G1/YVdzqPdX1D1S/NMLg28gKLnr6Oef8CcOA36a7FeZgVoEd9aY
         Zv/qq/e/Xx5A+PeZMZiD2otBcVk/6rja8kCt8=
MIME-Version: 1.0
In-Reply-To: <4D95B6AB.30608@templeet.org>
References: <4D95B6AB.30608@templeet.org>
Date: Fri, 1 Apr 2011 15:20:31 +0200
Message-ID: <AANLkTin+cCYoEiWyp=oc9byPG=yWBQ5NsmCae24U7vzr@mail.gmail.com>
To: Pascal COURTOIS <courtois@templeet.org>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] how to find a memory corruption in php ?
From: pierre.php@gmail.com (Pierre Joye)

hi,

In php 5.3+ the memory limit default is 256MB, not 128MB. 5.3 does not
necessary use more memory but actually uses and reports its usage more
efficiently. I would suggest to use this default value and try again.

About detecting leaks and memory corruptions, valgrind is a good tool
to begin with.

Cheers,

On Fri, Apr 1, 2011 at 1:27 PM, Pascal COURTOIS <courtois@templeet.org> wrote:
> Hi all,
>
> I get an error with my program:
> Fatal error: Allowed memory size of 134217728 bytes exhausted at /home/courtois/php-5.3.6/Zend/zend_execute.h:163 (tried to allocate 261900 bytes) in /var/www/dev4.sociatomdev.com/chroot/htdocs/templeet/fetch.php on line 580
>
>
> - The same error occurs with any of php 5.3 versions tested. With 5.2 it's ok.
> - I know the error message is wrong. The program does not consume much memory.
> - If i change some lines in my php code like adding trace messages it sometimes work sometimes no (but constant result for same php code)
>
>
> I will not submit the bug since it's hard to reproduce unless being in the exact same configuration as me.
>
> I used to be an experienced C programmer (>300000 lines written) but almost nothing for the last 15 years.
>
> My questions:
> - is there any document somewhere to read before hunting a bug in php ?
> - are there any build/compile options other than --enable-debug ?
> - how should I proceed to debug when php is called via fastcgi ?
>
> My configuration: debian squeeze i386 32bits
>
> Thanks,
>
> Pascal
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org