iansmith wrote:
Usually that happens when mod_perl hasn't been compiled yet. Are you sure you have followed the right order of build as explained at the install page?On Thu, 19 Dec 2002, Stas Bekman wrote:Before you rebuild it, if you can get the segfault backtrace, that would be great. If you don't know how, check: http://perl.apache.org/docs/1.0/guide/help.html#How_to_Report_ProblemsTried to do a "make test" in the mod_perl directory and got... Syntax error on line 3 of mod_perl-1.27/t/conf/httpd.conf: Invalid command '=pod', perhaps mis-spelled or defined by a module not included in the server configuration
Any chance you can recompile mod_perl with DEBUG enabled and get the trace again, so that we can see the arguments to the faulty call?I did a manual run with gdb and got this when it crashed... Starting program: /var/www-1/source/apache_1.3.27/src/httpd -X [New Thread 8192 (LWP 5250)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8192 (LWP 5250)] #0 0x400c8dfd in perl_header_parser () from /var/www-1/libexec/libperl.so #1 0x0806acdd in run_method () #2 0x0806add7 in ap_header_parse () #3 0x0807f198 in process_request_internal () #4 0x0807f552 in ap_process_request () #5 0x08076816 in child_main () #6 0x080769b6 in make_child () #7 0x08076b1d in startup_children () #8 0x0807714a in standalone_main () #9 0x08077968 in main () #10 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6 Any ideas? Thanks.
--
__________________________________________________________________
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
