From: Carlos Lorenzo Matés (clmates_at_mundo-r.com)
Date: Thu May 17 2007 - 20:35:50 CEST
From: Carlos Lorenzo Matés <clmates@mundo-r.com> Date: Thu, 17 May 2007 20:35:50 +0200 Message-Id: <200705172035.54194.clmates@mundo-r.com> Subject: [suse-sles-e] SLES9 php crashing
Hi to all.
we are running an up to date SLES 9 sp3
last week we have upgraded our eGroupware version the the 1.4 version (1.4
RC1)
This application is the only php one we use in this server.
We are getting some messages saying this
*** glibc detected *** double free or corruption (fasttop): 0x092342c8 ***
*** glibc detected *** free(): invalid next size (fast): 0x0856f818 ***
*** glibc detected *** free(): invalid next size (fast): 0x08adeaa0 ***
[Wed May 16 17:15:16 2007] [notice] child pid 29015 exit signal Segmentation
fault (11)
Integer overflow in memory_limit check detected
*** glibc detected *** malloc(): memory corruption (fast): 0x0887a498 ***
[Wed May 16 17:15:46 2007] [notice] child pid 30292 exit signal Segmentation
fault (11)
*** glibc detected *** malloc(): memory corruption (fast): 0x087ec090 ***
[Wed May 16 17:15:57 2007] [notice] child pid 31948 exit signal Segmentation
fault (11)
*** glibc detected *** corrupted double-linked list: 0x08fb3860 ***
*** glibc detected *** corrupted double-linked list: 0x08fb3898 ***
[Wed May 16 17:16:18 2007] [notice] child pid 28313 exit signal Segmentation
fault (11)
*** glibc detected *** malloc(): memory corruption (fast): 0x08fb8558 ***
[Wed May 16 17:16:26 2007] [notice] child pid 31482 exit signal Segmentation
fault (11)
the php developers from egroupware toldme that this is a bug in our php
version.
how could i debug this further to report the bug?
is any way to make this debug more dense?
is any other user with this application runnig on an SLES 9 system?
many thanks
-- Un Saludo. Carlos Lorenzo Matés
This archive was generated by hypermail 2.1.7 : Thu May 17 2007 - 22:39:44 CEST