Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21431
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43BD14B4.3070705@iamjochem.com>
Date: Thu, 05 Jan 2006 13:44:36 +0100
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: php internals <internals@lists.php.net>
References: <43BA6FD4.4010103@iamjochem.com> <43BAA937.2000702@lerdorf.com>
In-Reply-To: <43BAA937.2000702@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] debugging APC - bit over my head; clue desired
From: jochem@iamjochem.com (Jochem Maas)

Rasmus,

I have a quick question which if you are able to
give an answer to will hopefully help to (finally)
create a repro. script for the afore mentioned apc segfault.

I am 99.9% sure that the apc opcode cache is not likely some/one
of my classes. but that leaves 194 odd files to check (upto 200,000
lines of code) and I have no idea where to begin. so the question is
do you know of any class related syntax (or whatever) that is _likely_
to be causing the segfaulting?

a hint about the most likely place to start looking (e.g.
inheritance, interface implementation, method visibility, etc)
would be very welcome. of course I can understand if you felt that
there was no one 'thing' more likely to be the culprit than another.

kind rgds,
Jochem


Rasmus Lerdorf wrote:
> Jochem Maas wrote:
> 
>> a while back I was asking about APC - I have a problem with php
>> seghfaulting when I use APC _and_ turn on the opcode cache (apc_store()
>> and apc_fetch() work very well - I'm sticking _lots_ of 'ResultSet' 
>> objects
>> in there for instance and it works very nicely) 
> 
> 
> Note that caching arrays is way faster than caching objects, so if at 
> all possible, convert your ResultSet object to an associative array 
> before storing it.
> 
> To fix your segfault I'll need a short PHP script that reproduces the 
> problem.  On one hand I bet an <?php echo "hello world"?> script doesn't 
> crash it, and on the other you have whatever code you are running that 
> does.  Step up from Hello World slowly until it starts crashing and send 
> me that.



> 
> -Rasmus
>