On Wed, Feb 14, 2007 at 11:16:22AM -0800, Frederic Wenzel wrote: > >> I made a stack backtrace in the related wordpress ticket > >> (http://trac.wordpress.org/ticket/3678) and it seems like this is not > >> a wordpress 2.1 issue: > >> http://trac.wordpress.org/attachment/ticket/3678/backtrace.24347
> >> I am running Debian Sarge on a VM (Kernel > >> 2.6.9-022stab078.14-enterprise) with libc6 2.3.2.ds1-22sarge4. > >> Apache 2.0.54, PHP 4.3.10, MySQL 4.1.11. > >The linked backtrace points to a PHP memory management problem. Do you > >also > >have any Zend extensions installed? Please forward your php.ini. > No, I don't have any additional extensions installed. My php.ini > should be quite the defaults, IIRC I just raised the memory limit. > It's attached (hope that works). Hmm. Noteworthy is the large number of PHP extensions you have loaded, even if you don't have any Zend extensions installed. Could you try commenting out any of these extensions not used by wordpress, and test whether that affects your crash? If it does, please uncomment the extensions one by one until the problem shows up again, then send that list of extensions. If it doesn't, please send the minimum list of extensions that need to be enabled for your wordpress instance to run. In either case, it would be a good idea to try running apache under valgrind to see if that permits pinning down the problem. Alternatively, you may want to try the php version from etch to see if this problem has resolved itself. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
