Re: What would cause a SEGFAULT on startup

["Tuc at T-B-O-H.NET" <suppressed>]

Hi,

	Thanks for the reply, but unfortunately I can't on both accounts.
I realize this sounds weird, because of certain issues I need to bring this
up like another server. The only reason difference was I wanted to see if I
could get threaded perl running on this one. 

	Over the weekend I backed down to regular perl, deleted and reinstalled
all my modules, and now modperl runs. 

	I'm going to suggest to the FREEBSD maintainer that he put a check
that if your running threaded perl, to stop the build.

			Thanks, Tuc

> 
> If you're starting modperl from scratch, I'd suggest that you go with 
> modperl2 on apache 2.2 than legacy apache 1.3 + modperl 1
> 
> Tuc at T-B-O-H.NET wrote:
> > Hi,
> >
> > 	I'm running :
> >
> >
> > apache+mod_ssl+mod_deflate-1.3.37+2.8.28
> > perl-threaded-5.8.8
> > mod_perl-1.30
> >
> > 	all installed via the FreeBSD ports collection.
> >
> > 	When I try to start it, using just the default httpd.conf
> > with nothing but it being loaded, I get a segfault. The backtrace is :
> >
> > (gdb) bt
> > #0  0x286e9350 in Perl_newSVpvn ()
> >    from /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> > #1  0x2873e1bd in PerlIO_open ()
> >    from /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> > #2  0x2868736a in S_open_script ()
> >    from /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> > #3  0x28684267 in S_parse_body ()
> >    from /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> > #4  0x286837fe in perl_parse ()
> >    from /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so
> > #5  0x2861ddb4 in perl_startup () from /usr/local/libexec/apache/libperl.so
> > #6  0x2861d82a in perl_module_init () from /usr/local/libexec/apache/libperl.so
> > #7  0x0805683e in ap_init_modules ()
> > #8  0x0805f5df in main ()
> >
> >
> > 	Is this because I'm using threaded perl?  I know it was
> > an issue on FreeBSD at one time.
> >
> > 		Thanks, Tuc
> >   
>