Greg Rumple [EMAIL PROTECTED] wrote:
The test.pl script works fine by it's self. Turning on full PERL
debugging/tracing yields that the actual script has fully finished, and
that it's in the tear down of the actualy perl stuff that this failure
is coming from. Not from the script per se.
* David Kaufman ([EMAIL PROTECTED]) [020728 00:55]:
again, just a shot in the dark, but why not try the more mod_perl specific
Apache::DBI instead of plain ole DBI?
Okay I have tried this. I also edited the Apache/DBI.pm and enabled
both Apache::DBI and DBI debugging at level 2 so I could get
Hey Greg et al.
I'd betcha your problem is almost certainly caused by your use of DSOs. If
you *really* want to prune your system down to see where your bug is, then
build apache and mod_perl statically. There was a very well-known bug that
caused DBI to segfault if it was run under a DSO.
Yup, this is it. If I build it without DSO support, it appears to work.
Of course I build this with mod_php, mod_ssl, mod_perl, and a couple of
custom modules. So running without DSO support isn't to easy. I guess
I can attempt to build mod_perl in, but keep DSO support and dynamic
load the
There are well written instructions in The Guide that show step by step how
to roll a static mod_perl/php/ssl binary. And I've done it personally
without much trouble, so it's easier than you might think. ;-) Here's the
direct link:
I actually was successful at building apache/mod_perl static with DSO
support and not having to change the rest of the modules. It appears to
be working, so will continue to test further.
Greg
* Drew Taylor ([EMAIL PROTECTED]) [020728 22:19]:
There are well written instructions in The Guide
Okay, I've been staring at this problem for close to 48 hours straight
now and have finally narrowed it down to a set of lines of code.
So let me first expand.
I currently have a system running, with Apache 1.3.14 and Mod_Perl 1.24
on Redhat 7.0 (yeah REALLY REALLY ancient) and Perl 5.005003.
