I also have been experiencing this problem. What has been doubly frustrating
is that the Apache server sitting next the troubled one is running exactly
the same scripts and runs faultlessly.
The difference between the two Apaches is that the working one is only
compiled with modperl (as a static module) whereas the crashing one has
modphp4, modjk, moddav and few others. The faulty one is 5MB and the working
one is only 1.3MB. I read recently that other people have noted a conflict
between modperl and modphp
(http://slashdot.org/apache/00/11/21/1720242.shtml) so as a workaround you
might consider building Apache with modperl statically linked and omitting
any other modules for the moment (perhaps switch the Port to 8080 for this
version).
The slashdot article also mentions ApacheToolbox which I find invaluable for
getting all the conflicting settings right for Apache builds.
HTH
Gary Ashton-Jones
-----Original Message-----
Subject: Segmentation fault in apache child when calling DBI::connect
Author: Luis Henrique Cassis Fagundes <[EMAIL PROTECTED]>
Date: Tue, 09 Jan 2001 09:49:26 +0100
I use apache1.3.12 with mod_perl 1.24 and I've been using it in several
programs with DBI (version 1.13). This is the first time I get an error
like this, other programs that uses DBI are still working.
In command line everything is working ok, but when I run my program under
mod_perl, I get no data (not even headers), and the only message in the
error log (with LogLevel debug) is this:
[Tue Jan 9 09:40:54 2001] [notice] child pid 28932 exit signal
Segmentation fault (11)
I've debugged everything and discovered that the error occurs when I call
DBI->connect. I debbuged DBI.pm and DBD/mysql.pm and found that the
error happens in the following line, in DBD::mysql (version 2.0402):
DBD::mysql::db::_login($this, $dsn, $username, $password)
or $this = undef
I've tried also to connect to different databases in different servers,
but the error persists. Does anyone have any idea of how to solve this?
Thanks a lot.
[]s
Luis
