Bug #1509: Seg Fault in mySqldatabase connection Mod_Perl1.19/PHP3.0.7/Apache1.3.6

From: Date: Tue, 08 Jun 1999 12:51:58 +0000
Subject: Bug #1509: Seg Fault in mySqldatabase connection Mod_Perl1.19/PHP3.0.7/Apache1.3.6
Groups: php.dev 
Request: Send a blank email to php-dev+get-6710@lists.php.net to get a copy of this message
From: d@kleber.net Operating system: Redhat 5.2/5.0 Glibc 2.0.7-29 PHP version: 3.0.7 PHP Bug Type: Reproduceable crash Bug description: Seg Fault in mySqldatabase connection Mod_Perl1.19/PHP3.0.7/Apache1.3.6 When I compile Aapche 1.3.6 on Redhat Linux (5.0 or 5.2) for intel with the following statically linked modules Mod_Perl 1.19 PHP3.0.7 Mod_SSL 2.3.0 - 1.3.6 Jserv 1.0b5 MySql 3.22.22 Perl 5.004_05 There is no php.ini I can no longer access .iphtml files (.html files parsed using eperl 2.2.14) which use the perl DBI module (loaded into mod_perl/apache's memory space at startup time). The child process dies with a segementation fault and the browser responds with a 'document contained no data' error. This also occurs when I compile without Jserv, and when I configure PHP without an awareness to mysql's presence. .iphtml files without database connects in them work as expected, and if I compile without PHP all scripts work correctly. I know that it seems like overkill to compile both PHP and Mod_perl into the server, but we have several users who can be trusted to develop PHP scripts, but not CGI/iphtml or other perl scripts, and we also have to develop for a number of different server setups. Has anyone succsesfully compiled Mod_Perl/PHP/Apache into one static httpd binary which works? I can't find much mention of it anywhere... is there a specifc order they should be compiled in? Or am I just asking too much?

« previous php.dev (#6710) next »