You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Alexey Slynko <sl...@tronet.ru> on 2003/04/09 14:31:14 UTC
Mod_perl segmentation fault
I've got some trouble with mod_perl-1.27 and Apache/1.3.27. When
I try to use module Apache::Status (section "Signal Handlers"),
apache say "child pid 16713 exit signal Segmentation fault (11)".
Debug info:
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4, sstr=0x119,
flags=2)
at sv.c:3565
3565 stype = SvTYPE(sstr);
(gdb) bt
#0 0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4,
sstr=0x119, flags=2)
at sv.c:3565
#1 0x0812f912 in Perl_magic_getsig (sv=0x82359f4, mg=0x8239828)
at mg.c:1040
#2 0x0812ddff in Perl_mg_get (sv=0x82359f4) at mg.c:124
#3 0x0814aea2 in Perl_sv_setsv_flags (dstr=0x85986dc,
sstr=0x82359f4, flags=2)
at sv.c:3710
#4 0x08150565 in Perl_sv_mortalcopy (oldstr=0x82359f4) at
sv.c:6229
#5 0x08140695 in Perl_pp_helem () at pp_hot.c:1717
#6 0x08127e89 in Perl_runops_debug () at dump.c:1398
#7 0x080decc8 in S_call_body (myop=0xbffff1b0, is_eval=0) at
perl.c:2045
#8 0x080de98f in Perl_call_sv (sv=0x82174e0, flags=4) at
perl.c:1963
#9 0x08089369 in perl_call_handler (sv=0x82174e0, r=0x8648aec,
args=0x0)
at mod_perl.c:1658
#10 0x08088896 in perl_run_stacked_handlers (hook=0x81bd967
"PerlHandler",
r=0x8648aec, handlers=0x83a0684) at mod_perl.c:1371
#11 0x080862e1 in perl_handler (r=0x8648aec) at mod_perl.c:897
#12 0x080b0253 in ap_invoke_handler (r=0x8648aec) at
http_config.c:518
#13 0x080c5beb in process_request_internal (r=0x8648aec) at
http_request.c:1308
#14 0x080c5c4a in ap_process_request (r=0x8648aec) at
http_request.c:1324
#15 0x080bb9e2 in child_main (child_num_arg=0) at
http_main.c:4603
#16 0x080bbb82 in make_child (s=0x81fe44c, slot=0,
now=1049890548)
at http_main.c:4718
#17 0x080bbce8 in startup_children (number_to_start=2) at
http_main.c:4800
---Type <return> to continue, or q <return> to quit---
#18 0x080bc313 in standalone_main (argc=3, argv=0xbffff544) at
http_main.c:5108
#19 0x080bcb31 in main (argc=3, argv=0xbffff544) at
http_main.c:5456
#20 0x400a2bb4 in __libc_start_main () from /lib/libc.so.6
(gdb)
Perl info:
Summary of my perl5 (revision 5.0 version 8 subversion 0)
configuration:
Platform:
osname=linux, osvers=2.4.20, archname=i686-linux
uname='linux mira 2.4.20 #1 sun apr 6 20:29:45 msd 2003 i686
unknown '
config_args='-Doptimize=-g'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=define d_sfio=undef uselargefiles=define
usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags ='-DDEBUGGING -fno-strict-aliasing
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
optimize='-g',
cppflags='-DDEBUGGING -fno-strict-aliasing'
ccversion='', gccversion='3.2.2', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8,
byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define,
longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8,
Off_t='off_t', lseeksize=8
alignbytes=4, prototype=define
Linker and Libraries:
ld='cc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil
perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
libc=/lib/libc-2.3.1.so, so=so, useshrplib=false,
libperl=libperl.a
gnulibc_version='2.3.1'
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef,
ccdlflags='-rdynamic'
cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: DEBUGGING USE_LARGE_FILES
Built under linux
Compiled at Apr 9 2003 15:53:29
@INC:
/usr/local/lib/perl5/5.8.0/i686-linux
/usr/local/lib/perl5/5.8.0
/usr/local/lib/perl5/site_perl/5.8.0/i686-linux
/usr/local/lib/perl5/site_perl/5.8.0
/usr/local/lib/perl5/site_perl
.
Apache linked with mod_perl statically
Any ideas ?
Alexey Slynko
E-mail: slynko@tronet.ru
Re: Mod_perl segmentation fault
Posted by Oleg Bartunov <ol...@sai.msu.su>.
Seems it's fixed in current 5.8.X.
Oleg
On Thu, 10 Apr 2003, Oleg Bartunov wrote:
> On Thu, 10 Apr 2003, Stas Bekman wrote:
>
> > Oleg Bartunov wrote:
> > > Stas,
> > >
> > > I successfully reproduced segmentation fault running your example
> > > from command line. This happens on clean Slackware 9.0 insttallation.
> > > How it's safe to use perl 5.8.0 in production ?
> >
> > Fantastic! Now run the perlbug script to submit the bug report to p5p.
> >
>
> Just sent it.
>
>
> > > How it's safe to use perl 5.8.0 in production ?
> >
> > In general I haven't heard about problems regarding safety/stability of 5.8.0.
> > But I'm the wrong person to ask, as I don't run any production sites at this
> > moment.
> >
> > 5.8.0 is much much better than 5.6.0 was (bug-wise), but still quite a few
> > bugs were reported to p5p, which could be totally irrelevant to your
> > particular applications.
> >
> > Jarkko is planning 5.8.1 to be released quite soon I believe.
> >
>
> My report is very much to the point :-)
>
> Thanks for help, Stas
>
> > __________________________________________________________________
> > Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
> > http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> > mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> > http://modperlbook.org http://apache.org http://ticketmaster.com
> >
>
> Regards,
> Oleg
> _____________________________________________________________
> Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
> Sternberg Astronomical Institute, Moscow University (Russia)
> Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
> phone: +007(095)939-16-83, +007(095)939-23-83
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
Re: Mod_perl segmentation fault
Posted by Oleg Bartunov <ol...@sai.msu.su>.
On Thu, 10 Apr 2003, Stas Bekman wrote:
> Oleg Bartunov wrote:
> > Stas,
> >
> > I successfully reproduced segmentation fault running your example
> > from command line. This happens on clean Slackware 9.0 insttallation.
> > How it's safe to use perl 5.8.0 in production ?
>
> Fantastic! Now run the perlbug script to submit the bug report to p5p.
>
Just sent it.
> > How it's safe to use perl 5.8.0 in production ?
>
> In general I haven't heard about problems regarding safety/stability of 5.8.0.
> But I'm the wrong person to ask, as I don't run any production sites at this
> moment.
>
> 5.8.0 is much much better than 5.6.0 was (bug-wise), but still quite a few
> bugs were reported to p5p, which could be totally irrelevant to your
> particular applications.
>
> Jarkko is planning 5.8.1 to be released quite soon I believe.
>
My report is very much to the point :-)
Thanks for help, Stas
> __________________________________________________________________
> Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
Re: Mod_perl segmentation fault
Posted by Stas Bekman <st...@stason.org>.
Oleg Bartunov wrote:
> Stas,
>
> I successfully reproduced segmentation fault running your example
> from command line. This happens on clean Slackware 9.0 insttallation.
> How it's safe to use perl 5.8.0 in production ?
Fantastic! Now run the perlbug script to submit the bug report to p5p.
> How it's safe to use perl 5.8.0 in production ?
In general I haven't heard about problems regarding safety/stability of 5.8.0.
But I'm the wrong person to ask, as I don't run any production sites at this
moment.
5.8.0 is much much better than 5.6.0 was (bug-wise), but still quite a few
bugs were reported to p5p, which could be totally irrelevant to your
particular applications.
Jarkko is planning 5.8.1 to be released quite soon I believe.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: Mod_perl segmentation fault
Posted by Oleg Bartunov <ol...@sai.msu.su>.
Stas,
I successfully reproduced segmentation fault running your example
from command line. This happens on clean Slackware 9.0 insttallation.
How it's safe to use perl 5.8.0 in production ?
Oleg
On Thu, 10 Apr 2003, Stas Bekman wrote:
> Alexey Slynko wrote:
> > I've got some trouble with mod_perl-1.27 and Apache/1.3.27. When
> > I try to use module Apache::Status (section "Signal Handlers"),
> > apache say "child pid 16713 exit signal Segmentation fault (11)".
> >
> > Debug info:
> >
> > (gdb) continue
> > Continuing.
> >
>
> That looks like a bug in perl-5.8.0. You probably need to report it to p5p.
>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4, sstr=0x119,
> > flags=2)
> > at sv.c:3565
> > 3565 stype = SvTYPE(sstr);
> > (gdb) bt
> > #0 0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4,
> > sstr=0x119, flags=2)
> ^^^^^
> this is a bogus pointer to SV, coming from:
>
> > at sv.c:3565
> > #1 0x0812f912 in Perl_magic_getsig (sv=0x82359f4, mg=0x8239828)
> > at mg.c:1040
>
> if(PL_psig_ptr[i])
> sv_setsv(sv,PL_psig_ptr[i]);
>
> PL_psig_ptr[i] seems to be corrupted, though I can't tell what's value of 'i'.
> If you use Apache::DB you may interactively debug it, by setting a bp in
> perl_call_handler(). Does your code set some signal handlers?
>
> Of course may be someone at p5p will know right away what the problem is.
>
> I don't think modperl messes with PL_psig_ptr[i].
>
> It'll probably help p5p if you can reproduce the problem outside mod_perl.
> e.g. try running a script (rewritten for command line from Apache::Status):
>
> use Symbol;
> for (sort keys %SIG) {
> my $val = $SIG{$_} || "";
> if ($val and ref $val eq "CODE") {
> if (my $cv = Symbol->can('sv_name')) {
> $val = "\\&". $cv->($val);
> }
> }
> print "$_ = $val\n";
> }
>
> but I can't see a problem on my box
>
> > #2 0x0812ddff in Perl_mg_get (sv=0x82359f4) at mg.c:124
> > #3 0x0814aea2 in Perl_sv_setsv_flags (dstr=0x85986dc,
> > sstr=0x82359f4, flags=2)
> > at sv.c:3710
> > #4 0x08150565 in Perl_sv_mortalcopy (oldstr=0x82359f4) at
> > sv.c:6229
> > #5 0x08140695 in Perl_pp_helem () at pp_hot.c:1717
> > #6 0x08127e89 in Perl_runops_debug () at dump.c:1398
> > #7 0x080decc8 in S_call_body (myop=0xbffff1b0, is_eval=0) at
> > perl.c:2045
> > #8 0x080de98f in Perl_call_sv (sv=0x82174e0, flags=4) at
> > perl.c:1963
> > #9 0x08089369 in perl_call_handler (sv=0x82174e0, r=0x8648aec,
> > args=0x0)
> > at mod_perl.c:1658
> > #10 0x08088896 in perl_run_stacked_handlers (hook=0x81bd967
> > "PerlHandler",
> > r=0x8648aec, handlers=0x83a0684) at mod_perl.c:1371
> > #11 0x080862e1 in perl_handler (r=0x8648aec) at mod_perl.c:897
> > #12 0x080b0253 in ap_invoke_handler (r=0x8648aec) at
> > http_config.c:518
> > #13 0x080c5beb in process_request_internal (r=0x8648aec) at
> > http_request.c:1308
> > #14 0x080c5c4a in ap_process_request (r=0x8648aec) at
> > http_request.c:1324
> > #15 0x080bb9e2 in child_main (child_num_arg=0) at
> > http_main.c:4603
> > #16 0x080bbb82 in make_child (s=0x81fe44c, slot=0,
> > now=1049890548)
> > at http_main.c:4718
> > #17 0x080bbce8 in startup_children (number_to_start=2) at
> > http_main.c:4800
> > ---Type <return> to continue, or q <return> to quit---
> > #18 0x080bc313 in standalone_main (argc=3, argv=0xbffff544) at
> > http_main.c:5108
> > #19 0x080bcb31 in main (argc=3, argv=0xbffff544) at
> > http_main.c:5456
> > #20 0x400a2bb4 in __libc_start_main () from /lib/libc.so.6
> > (gdb)
> >
> > Perl info:
> >
> > Summary of my perl5 (revision 5.0 version 8 subversion 0)
> > configuration:
> > Platform:
> > osname=linux, osvers=2.4.20, archname=i686-linux
> > uname='linux mira 2.4.20 #1 sun apr 6 20:29:45 msd 2003 i686
> > unknown '
> > config_args='-Doptimize=-g'
> > hint=recommended, useposix=true, d_sigaction=define
> > usethreads=undef use5005threads=undef useithreads=undef
> > usemultiplicity=undef
> > useperlio=define d_sfio=undef uselargefiles=define
> > usesocks=undef
> > use64bitint=undef use64bitall=undef uselongdouble=undef
> > usemymalloc=n, bincompat5005=undef
> > Compiler:
> > cc='cc', ccflags ='-DDEBUGGING -fno-strict-aliasing
> > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
> > optimize='-g',
> > cppflags='-DDEBUGGING -fno-strict-aliasing'
> > ccversion='', gccversion='3.2.2', gccosandvers=''
> > intsize=4, longsize=4, ptrsize=4, doublesize=8,
> > byteorder=1234
> > d_longlong=define, longlongsize=8, d_longdbl=define,
> > longdblsize=12
> > ivtype='long', ivsize=4, nvtype='double', nvsize=8,
> > Off_t='off_t', lseeksize=8
> > alignbytes=4, prototype=define
> > Linker and Libraries:
> > ld='cc', ldflags =' -L/usr/local/lib'
> > libpth=/usr/local/lib /lib /usr/lib
> > libs=-lnsl -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil
> > perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
> > libc=/lib/libc-2.3.1.so, so=so, useshrplib=false,
> > libperl=libperl.a
> > gnulibc_version='2.3.1'
> > Dynamic Linking:
> > dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef,
> > ccdlflags='-rdynamic'
> > cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
> >
> >
> > Characteristics of this binary (from libperl):
> > Compile-time options: DEBUGGING USE_LARGE_FILES
> > Built under linux
> > Compiled at Apr 9 2003 15:53:29
> > @INC:
> > /usr/local/lib/perl5/5.8.0/i686-linux
> > /usr/local/lib/perl5/5.8.0
> > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux
> > /usr/local/lib/perl5/site_perl/5.8.0
> > /usr/local/lib/perl5/site_perl
> > .
> >
> > Apache linked with mod_perl statically
> >
> > Any ideas ?
> > Alexey Slynko
> > E-mail: slynko@tronet.ru
>
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
Re: Mod_perl segmentation fault
Posted by Stas Bekman <st...@stason.org>.
Alexey Slynko wrote:
> I've got some trouble with mod_perl-1.27 and Apache/1.3.27. When
> I try to use module Apache::Status (section "Signal Handlers"),
> apache say "child pid 16713 exit signal Segmentation fault (11)".
>
> Debug info:
>
> (gdb) continue
> Continuing.
>
That looks like a bug in perl-5.8.0. You probably need to report it to p5p.
> Program received signal SIGSEGV, Segmentation fault.
> 0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4, sstr=0x119,
> flags=2)
> at sv.c:3565
> 3565 stype = SvTYPE(sstr);
> (gdb) bt
> #0 0x0814a852 in Perl_sv_setsv_flags (dstr=0x82359f4,
> sstr=0x119, flags=2)
^^^^^
this is a bogus pointer to SV, coming from:
> at sv.c:3565
> #1 0x0812f912 in Perl_magic_getsig (sv=0x82359f4, mg=0x8239828)
> at mg.c:1040
if(PL_psig_ptr[i])
sv_setsv(sv,PL_psig_ptr[i]);
PL_psig_ptr[i] seems to be corrupted, though I can't tell what's value of 'i'.
If you use Apache::DB you may interactively debug it, by setting a bp in
perl_call_handler(). Does your code set some signal handlers?
Of course may be someone at p5p will know right away what the problem is.
I don't think modperl messes with PL_psig_ptr[i].
It'll probably help p5p if you can reproduce the problem outside mod_perl.
e.g. try running a script (rewritten for command line from Apache::Status):
use Symbol;
for (sort keys %SIG) {
my $val = $SIG{$_} || "";
if ($val and ref $val eq "CODE") {
if (my $cv = Symbol->can('sv_name')) {
$val = "\\&". $cv->($val);
}
}
print "$_ = $val\n";
}
but I can't see a problem on my box
> #2 0x0812ddff in Perl_mg_get (sv=0x82359f4) at mg.c:124
> #3 0x0814aea2 in Perl_sv_setsv_flags (dstr=0x85986dc,
> sstr=0x82359f4, flags=2)
> at sv.c:3710
> #4 0x08150565 in Perl_sv_mortalcopy (oldstr=0x82359f4) at
> sv.c:6229
> #5 0x08140695 in Perl_pp_helem () at pp_hot.c:1717
> #6 0x08127e89 in Perl_runops_debug () at dump.c:1398
> #7 0x080decc8 in S_call_body (myop=0xbffff1b0, is_eval=0) at
> perl.c:2045
> #8 0x080de98f in Perl_call_sv (sv=0x82174e0, flags=4) at
> perl.c:1963
> #9 0x08089369 in perl_call_handler (sv=0x82174e0, r=0x8648aec,
> args=0x0)
> at mod_perl.c:1658
> #10 0x08088896 in perl_run_stacked_handlers (hook=0x81bd967
> "PerlHandler",
> r=0x8648aec, handlers=0x83a0684) at mod_perl.c:1371
> #11 0x080862e1 in perl_handler (r=0x8648aec) at mod_perl.c:897
> #12 0x080b0253 in ap_invoke_handler (r=0x8648aec) at
> http_config.c:518
> #13 0x080c5beb in process_request_internal (r=0x8648aec) at
> http_request.c:1308
> #14 0x080c5c4a in ap_process_request (r=0x8648aec) at
> http_request.c:1324
> #15 0x080bb9e2 in child_main (child_num_arg=0) at
> http_main.c:4603
> #16 0x080bbb82 in make_child (s=0x81fe44c, slot=0,
> now=1049890548)
> at http_main.c:4718
> #17 0x080bbce8 in startup_children (number_to_start=2) at
> http_main.c:4800
> ---Type <return> to continue, or q <return> to quit---
> #18 0x080bc313 in standalone_main (argc=3, argv=0xbffff544) at
> http_main.c:5108
> #19 0x080bcb31 in main (argc=3, argv=0xbffff544) at
> http_main.c:5456
> #20 0x400a2bb4 in __libc_start_main () from /lib/libc.so.6
> (gdb)
>
> Perl info:
>
> Summary of my perl5 (revision 5.0 version 8 subversion 0)
> configuration:
> Platform:
> osname=linux, osvers=2.4.20, archname=i686-linux
> uname='linux mira 2.4.20 #1 sun apr 6 20:29:45 msd 2003 i686
> unknown '
> config_args='-Doptimize=-g'
> hint=recommended, useposix=true, d_sigaction=define
> usethreads=undef use5005threads=undef useithreads=undef
> usemultiplicity=undef
> useperlio=define d_sfio=undef uselargefiles=define
> usesocks=undef
> use64bitint=undef use64bitall=undef uselongdouble=undef
> usemymalloc=n, bincompat5005=undef
> Compiler:
> cc='cc', ccflags ='-DDEBUGGING -fno-strict-aliasing
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
> optimize='-g',
> cppflags='-DDEBUGGING -fno-strict-aliasing'
> ccversion='', gccversion='3.2.2', gccosandvers=''
> intsize=4, longsize=4, ptrsize=4, doublesize=8,
> byteorder=1234
> d_longlong=define, longlongsize=8, d_longdbl=define,
> longdblsize=12
> ivtype='long', ivsize=4, nvtype='double', nvsize=8,
> Off_t='off_t', lseeksize=8
> alignbytes=4, prototype=define
> Linker and Libraries:
> ld='cc', ldflags =' -L/usr/local/lib'
> libpth=/usr/local/lib /lib /usr/lib
> libs=-lnsl -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil
> perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
> libc=/lib/libc-2.3.1.so, so=so, useshrplib=false,
> libperl=libperl.a
> gnulibc_version='2.3.1'
> Dynamic Linking:
> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef,
> ccdlflags='-rdynamic'
> cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
>
>
> Characteristics of this binary (from libperl):
> Compile-time options: DEBUGGING USE_LARGE_FILES
> Built under linux
> Compiled at Apr 9 2003 15:53:29
> @INC:
> /usr/local/lib/perl5/5.8.0/i686-linux
> /usr/local/lib/perl5/5.8.0
> /usr/local/lib/perl5/site_perl/5.8.0/i686-linux
> /usr/local/lib/perl5/site_perl/5.8.0
> /usr/local/lib/perl5/site_perl
> .
>
> Apache linked with mod_perl statically
>
> Any ideas ?
> Alexey Slynko
> E-mail: slynko@tronet.ru
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: Mod_perl segmentation fault
Posted by Aaron Trevena <aa...@tuskerdirect.com>.
Alexey Slynko wrote:
>I've got some trouble with mod_perl-1.27 and Apache/1.3.27. When
>I try to use module Apache::Status (section "Signal Handlers"),
>apache say "child pid 16713 exit signal Segmentation fault (11)".
>
>
Have you tried with different startup.pl files ?
we managed to track down our problem by eliminating parts of the startup
file until we got two modules that when 'use'd in a specific order
caused a segfault.
it is worth trying out some stripped down startup files, and handlers to
see if you can isolate the problem.
cheers,
A.
Re: Mod_perl segmentation fault
Posted by Ged Haywood <ge...@www2.jubileegroup.co.uk>.
Hi there,
On Wed, 9 Apr 2003, Alexey Slynko wrote:
> I've got some trouble with mod_perl-1.27 and Apache/1.3.27. When
> I try to use module Apache::Status (section "Signal Handlers"),
> apache say "child pid 16713 exit signal Segmentation fault (11)".
> Characteristics of this binary (from libperl):
> Compile-time options: DEBUGGING USE_LARGE_FILES
In addition to the other suggestions, you might want to look into
USE_LARGE_FILES in the archives. Have you been using Perl 5.8.0 for
very long? There might be interesting things in the archives about
that too.
73,
Ged.