> If the segfault was the same everytime it should be easy to track > down, but I've had a large amount of different segfaults running > apache through gdb. The other thing is that one screen can be loaded > different times before the segfault comes as well, sometimes the > segfault comes straight away, other times after 5-6 reloads of the > same screen.
This tends to be the sort of problem where Valgrind can be very useful. It sounds like memory corruption somewhere. Run it like this: valgrind --leak-check=yes --show-reachable=yes --num-callers=16 --error-limit=no --tool=memcheck --logfile=out /usr/bin/apache -X Then hit the server and have a look at the out.<pid> file. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
