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 in Perl_pp_require () from /opt/prod/apache/modules/mod_perl.so
#7 0xdeb226a1 in modperl_pp_require () at modperl_perl_pp.c:69
#8 0xdeb6d61e in Perl_runops_standard ()
from /opt/prod/apache/modules/mod_perl.so
#9 0xdeb31361 in S_call_body () from /opt/prod/apache/modules/mod_perl.so
Stas Bekman 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 better use the attachment in this message:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=111145170703909&w=2
it's already designed for this specific problem. Just swap my setup with yours.
Please don't hesitate to ask questions if you have any, Vincent.
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 conf file to try and reproduced how my httpd.conf file is set up and again no segfaults. Should I go the whole way and add the entire contents of my httpd.conf file to the test conf file? Or is there some other approach I should take in order to reproduce the problem?
