http://www.mail-archive.com/modperl@apache.org/msg27132.html
led me in the right direction. Instead of recompiling, I'm simply not use'ing XML::LibXSLT globally.
I apologize for the list noise; it was late at night (or _really_ early in the morning, depending on your perspective)...yeah, that's a good excuse. :)
-man
Stas Bekman wrote:
Michael A Nachbaur wrote:I'm pulling my hair out. I have an extremely complicated <Perl> section that I'm trying to load in Apache, and I'm having one hell of a time debugging everything.
To make a long story short, I'm defining multiple virtualhosts that each are configured to run AxKit. I have my Perl section defined in a separate file, and Include it into my main httpd.conf. I have some debugging code that dumps the PerlSections data to STDOUT when the server starts up. When Apache starts, it dies silently with a core dump (after outputting the Data::Dumper representation of my PerlSections).
If I copy/paste the outputted Perl code and re-munge it into Apache's configuration syntax and include this file, the server starts without a problem. Therefore, I know there isn't a problem with the modules I'm loading in the virtualhosts, but I can't seem to track the problem down because I can't get any debugging information.
First of all I assume that you are talking about mod_perl 1.0 here.
You need to get a core file and send in the backtrace as explained here:
http://perl.apache.org/docs/1.0/guide/help.html#How_to_Report_Problems
If you can't get it see the tips at:
http://perl.apache.org/docs/2.0/devel/debug/c.html#Getting_the_core_File_Dumped
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
