Yes, I'd be interested in this, too. I filed a bug report for a
segfault under similar conditions and I'd be happy to help find the
bug if I had any idea how to help...
Alan
On Jan 5, 2006, at 7:44 AM, Jochem Maas wrote:
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
--
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
