have an intereresting problem.... and a solution I'm not too happy with...
problem :
we have a modperl startup file that calls all the usual perl modules (Apache::Registry, etc) and Apache::DBI.
we want to ensure that we can disable apache::dbi before we upgrade the module on the live server (in case the new version has issues with our system and/or oracle).
so naturally we tried out a startup.pl script on the RC box (same machine, same apache binary, different IP, logdir, rootdir, etc) that had all Apache::DBI references commented out and teh server segfaults when started with or without -X but works just fine with the original startup.pl file.
the server segfaults before any requests to the server are made
a quick grep through the perl modules and cgi scripts give no obvious references to apache::dbi
solution :
after much trimming of startup.pl we got down to this :
# segfault a go-go
use CGI qw(-compile);
use DBI;
# alive-alive-oh
use DBI;
use CGI qw(-compile);
anybody else having this problem or is it just us ?
Versions of stuff we're using
update
Looks like we are unable to reproduce this bug on a different box - using stock debian linux, must be the specific combination of apache modules.
very odd!
