Vincent Moneymaker wrote:
Vince Moneymaker wrote:
Okay, all of the tests are being passed. I have added the contents
of my startup.pl file to the modperl_startup.pl file and no segfaults
are occurring including even when I change the Handler.pm file as the
tests are being run on it. I have
Stas Bekman wrote:
I discovered what was causing the problem. Even though I had used the
following in the startup.pl file
use Apache2::Const -compile = ':common';
the Apache modules were segfaulting on the straight 'OK' constant
declarations in them.
Vincent, what do you mean by
Vincent Moneymaker wrote:
Stas Bekman wrote:
I discovered what was causing the problem. Even though I had used the
following in the startup.pl file
use Apache2::Const -compile = ':common';
the Apache modules were segfaulting on the straight 'OK' constant
declarations in them.
Vincent, what do you
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5. I
previously had problems using Apache::Reload with mod_perl 1.99_19 version
back in December and gave up trying to find a fix. I thought I would try
again with the RC5 version but after having
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with
mod_perl-2.0.0-RC5. I previously had problems using Apache::Reload
with mod_perl 1.99_19 version back in December and gave up trying to
find a fix. I thought I would try again with the RC5
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f in Perl_pp_require () from
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f in Perl_pp_require ()
Vincent Moneymaker wrote
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f
Vincent Moneymaker wrote:
OK, so yours crash is in require, Vincent. Any chance you could
prepare a tarball that reproduces the problem, so Philippe can
reproduce it easily?
Please grab the template from geoff's site:
http://people.apache.org/~geoff/Apache-Test-skeleton-mp2.tar.gz
In fact
Vince Moneymaker wrote:
Okay, all of the tests are being passed. I have added the contents of my
startup.pl file to the modperl_startup.pl file and no segfaults are
occurring including even when I change the Handler.pm file as the tests
are being run on it. I have also added some items to the
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5. I
previously had problems using Apache::Reload with mod_perl 1.99_19 version
back in December and gave up trying to find a fix. I thought I would try
again with the RC5 version but after having upgraded from mod_perl
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5.
I previously had problems using Apache::Reload with mod_perl 1.99_19
version back in December and gave up trying to find a fix. I thought I
would try again with the RC5 version but after having
12 matches
Mail list logo
