PHP 4.0 Bug #3228: Odd behaviour (sybase related?)

From: Date: Mon, 17 Jan 2000 04:51:07 +0000
Subject: PHP 4.0 Bug #3228: Odd behaviour (sybase related?)
Groups: php.dev 
Request: Send a blank email to php-dev+get-14694@lists.php.net to get a copy of this message
From: simon@airdmhor.gen.nz Operating system: Linux RH6, 2.2.5-22 kernel PHP version: 4.0 Latest CVS (16/01/2000) PHP Bug Type: Misbehaving function Bug description: Odd behaviour (sybase related?) Long time php4/cvs user, using the same build script as I always do. Very recently without sybase, but with it this time : ./configure --prefix=/home/simonr/www --with-apache=../apache_1.3.9 --enable-track-vars --enable-debugger --with-xml --with-pgsql --with-sybase-ct=/usr/sybase --with-gd --with-config-file-path=/home/simonr/www/conf/php.ini And I'm getting inconsistant results on the same script. It either : a) works fine, b) reports an error on a line that's in the middle of a comment (ie: Fatal error: Cannot redeclare class xxdebug in class.debug.php on line 3), or c) fails to respond to the HTTP request at all I'm also getting : [Mon Jan 17 17:43:45 2000] Script: '/home/simonr/www/htdocs/crash.php' --------------------------------------- php_sybase_ct.c(338) : Block 0x081DFF58 status: Beginning: Cached (allocated on php_sybase_ct.c:319, 8 bytes) End: OK --------------------------------------- [Mon Jan 17 17:43:45 2000] [notice] child pid 629 exit signal Segmentation fault (11) happening with trivial scripts. I'm still working on narrowing down exactly what code triggers it. Mostly the segfault doesn't generate a core file, and when it does, the backtrace only has 1 line - #0 0x8060bbd in ap_get_server_built () More soon.

« previous php.dev (#14694) next »