Thanks Tyler,
Unfortunately this wont fix my issue as my apache processes seg fault no
matter what type of file I request, whether its a mod_perl script, an
html file, or just a directory listing, if mod_perl is loaded apache seg
faults constantly. My apache, php, mod_ssl and mod_perl installs are all
built from source on this machine.
-Jon
Tyler MacDonald wrote:
Jon Keller <[EMAIL PROTECTED]> wrote:
I'm trying to build apache 1.3.34 and mod_perl 1.29 on a debian 3.1
machine and whenever mod_perl is loaded apache segfaults at any type of
request.
I had a similar problem with Apache2 and mod_perl2. It drove me
absolutely nuts. When I changed my code to use $r->print instead of just
"print", the problem went away.
Then my friend matthias' scripts started segfaulting after a debian
"apt-get dselect-upgrade". He solved his problem too, in a bizzare way.
Instead of calling
print $cgi->header,
He just did:
print "Content-Type: text/html\n\n";
And the problem went away.
Now that I've seen you have this problem... if either of the above
solutions apply to you, please let the list know what works... I used to
think it was something quirky about our homebrew apache/mod_perl
configurations (build scripts attached), but it could be something weird
with debian or just with how apache or mod_perl in general interact with it.
I'm starting to think it's more debian's fault, since you're using apache1
and we're using apache2.
- Tyler
