The core file actually have been created (although no 'Core dumped'
message anywhere during tests). That's the backtrace from
Modperl-Registry test:
[quote]
gdb /usr/local/apache2/bin/httpd -core t/core
GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix5.1.0.0"...
Core was generated by `httpd'.
Program terminated with signal 11, Segmentation fault.
#0 0x1003169c in sig_coredump (sig=11) at mpm_common.c:955
955 mpm_common.c: No such file or directory.
in mpm_common.c
(gdb) bt
#0 0x1003169c in sig_coredump (sig=11) at mpm_common.c:955
#1 <signal handler called>
#2 0xd201ab70 in mpxs_Apache__RequestRec_content_type (r=???, type=???)
at /home/bozy/src/modperl-2.0/xs/Apache/RequestRec/Apache__RequestRec.h:27
#3 0xd201b344 in XS_Apache__RequestRec_content_type (cv=0x204347d4) at
RequestRec.xs:155
#4 0xd1ea2924 in Perl_pp_entersub () from
/home/bozy/src/modperl-2.0/src/modules/perl/mod_perl.so
#5 0xd1f1b864 in Perl_runops_standard () from
/home/bozy/src/modperl-2.0/src/modules/perl/mod_perl.so
#6 0xd1ee31e4 in S_call_body () from
/home/bozy/src/modperl-2.0/src/modules/perl/mod_perl.so
#7 0xd1ee2e64 in Perl_call_sv () from
/home/bozy/src/modperl-2.0/src/modules/perl/mod_perl.so
#8 0xd1f58ef8 in modperl_callback (handler=0x2032af48, p=0x20d55920, r=0x20d55958,
s=0x20229130, args=0x2037acac)
at modperl_callback.c:99
#9 0xd1f5988c in modperl_callback_run_handlers (idx=6, type=4, r=0x20d55958, c=0x0,
s=0x20229130, pconf=0x0, plog=0x0, ptemp=0x0,
run_mode=MP_HOOK_RUN_FIRST) at modperl_callback.c:268
#10 0xd1f59b94 in modperl_callback_per_dir (idx=6, r=0x20d55958,
run_mode=MP_HOOK_RUN_FIRST) at modperl_callback.c:356
#11 0xd1f60fa0 in modperl_response_handler_run (r=0x20d55958, finish=0) at
mod_perl.c:905
#12 0xd1f61318 in modperl_response_handler_cgi (r=0x20d55958) at mod_perl.c:1000
#13 0x1000aadc in ap_run_handler (r=0x20d55958) at config.c:151
#14 0x1000b640 in ap_invoke_handler (r=0x20d55958) at config.c:358
#15 0x1002c128 in ap_process_request (r=0x20d55958) at http_request.c:246
#16 0x10038b9c in ap_process_http_connection (c=0x20d4d9f0) at http_core.c:250
#17 0x100343cc in ap_run_process_connection (c=0x20d4d9f0) at connection.c:42
#18 0x1002e988 in child_main (child_num_arg=0) at prefork.c:609
#19 0x1002eb4c in make_child (s=0x0, slot=2) at prefork.c:703
#20 0x1002eeb0 in perform_idle_server_maintenance (p=0x0) at prefork.c:838
#21 0x1002f5e4 in ap_mpm_run (_pconf=0x20007868, plog=0xffffffff, s=0x0) at
prefork.c:1039
#22 0x100012dc in main (argc=7, argv=0x2ff22964) at main.c:617
[unquote]
Regards
Alexey
SB> Alexey Bozrikov wrote:
SB> [taking the ModPerl-Registry branch of this multi-faced thread]
>> Now, make test in ModPerl-Registry yields some error messages:
SB> [...]
>> t/404.t 2 2 100.00% 1-2
>> t/bad_scripts.t 1 1 100.00% 1
>> t/basic.t 18 1 5.56% 17
>> t/cgi.t 2 1 50.00% 2
>> 2 tests skipped.
>> Failed 4/14 test scripts, 71.43% okay. 5/70 subtests failed, 92.86% okay.
>> [warning] server localhost:8529 shutdown
>> [warning] port 8529 still in use...
>> ...done
>> [ error] error running tests (please examine t/logs/error_log)
>> [unquote]
>>
>> The Apache error log contains following:
>>
>> [quote cat t/logs/error_log]
>> [Fri Jul 30 08:55:15 2004] [notice] Apache/2.0.49 (Unix)
>> mod_perl/1.99_15-dev Perl/v5.8.4 PHP/5.0.0 DAV/2 configured --
>> resuming normal operations
>> [Fri Jul 30 08:55:15 2004] [info] Server built: Jul 15 2004 12:00:32
>> [Fri Jul 30 08:55:15 2004] [debug] prefork.c(955): AcceptMutex: sysvsem (default:
>> sysvsem)
>>
>> *** The following error entry is expected and harmless ***
>> [Fri Jul 30 08:55:55 2004] [error]
>> /home/bozy/src/modperl-2.0/ModPerl-Registry/t/cgi-bin/cannot_be_found
>> not found or unable to stat
>> [Fri Jul 30 08:55:55 2004] [error] mpxs_Apache__RequestRec_print:
>> $r->print can't be called before the response phase during global
>> destruction.\n
>> [Fri Jul 30 08:55:56 2004] [notice] child pid 16168 exit signal Segmentation fault
>> (11)
SB> You have a few segfaults reported. could you arrange for core files to
SB> be allowed? Apache-Test is already doing that (ulimit -c unlimited), but
SB> it doesn't seem to have an affect. Do you know why?
SB> Once you get the core files, show us their backtraces.
SB> http://perl.apache.org/docs/2.0/user/help/help.html#Resolving_Segmentation_Faults
SB> Now while you are rebuilding things, please use the current modperl cvs,
SB> so we will be in sync. Thanks.
SB>
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
** Nothing is illegal until you get caught.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
