Hmm,
 have you built mod_perl with PERL_USELARGEFILES=0?

 I've got almost the same set up (RH7) running just fine.

On Wed, 14 Feb 2001, Gary Algier wrote:

> My children are segfaulting.
>
> I have:
>       Solaris 2.6 (w/all latest patches installed right after the OS)
>       Perl 5.6.0 (no largefiles, no threads)
>       Apache 1.3.17
>       modperl 1.25 (as a DSO)
>       gcc 2.95.2 (using Sun's as and ld)
>
> If I run apache leaving out:
>       LoadModule perl_module        libexec/libperl.so
>       AddModule mod_perl.c
> it runs just fine.  Put them in and the child seg faults.   I did manage
> to gdb the process and it says:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xef0a2e00 in perl_header_parser ()
> (gdb) where
> #0  0xef0a2e00 in perl_header_parser ()
> #1  0x20714 in run_method ()
> #2  0x208e4 in ap_header_parse ()
> #3  0x3d9bc in process_request_internal ()
> #4  0x3ded0 in ap_process_request ()
> #5  0x314c8 in child_main ()
> #6  0x31854 in make_child ()
> #7  0x31dcc in perform_idle_server_maintenance ()
> #8  0x32630 in standalone_main ()
> #9  0x32f64 in main ()
>
> Unfortunately, there are no debugging symbols so it is limited.  It wasn't
> easy getting this, though if it would help I will endeavor to rebuild
> everything with debugging symbols and try again.
>
> In general, I know that DSOs are working as I runtime load the max.  I also
> load php 4.0.4pl1 that way and it works.
>
> Any ideas?  Does the trace help?
>
>
>
> --
> Gary Algier, WB2FWZ       [EMAIL PROTECTED]           +1 856 787 2758
> Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054      Fax:+1 856 866 2033
>
>        A self-addressed envelope would be addressed "envelope."
>

Reply via email to