[moving that back to the list, so others can help and benefit from]
Alexey Bozrikov wrote:
Okay, we'll give it a try while I am far from being expert in debugging programs. I had a look at it yesterday night with 'truss' (an AIX equivalent of 'strace'), looks really like an endless stream of fcntl's, loadx__'s and lseek's to me, doubt if there was something of a value. Later on I thought I'd better have a look with gdb, at least gdb is something I used couple of times some 10 years ago. Now it looks less mystical, cause httpd just plain SIGSEGV's in mod_perl, while not producing core and with no signs of dying while ran as plain 't/TEST -verbose ...'. Under gdb, not only it SIGSEGVed, but produced core file as well! Now, this is what came out of 't/TEST -debug ...':
[quote]
powerpc bozy: /home/bozy/src/mod_perl-1.99_14 $ t/TEST -debug -apxs
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/local/bin/perl /home/bozy/src/mod_perl-1.99_14/t/TEST -debug -apxs
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"...
[Sun Jul 25 15:27:12 2004] [info] 28 Apache:: modules loaded
[Sun Jul 25 15:27:12 2004] [info] 5 APR:: modules loaded
[Sun Jul 25 15:27:12 2004] [info] base server + 17 vhosts ready to run tests
Program received signal SIGSEGV, Segmentation fault.
0xd0f592ec in modperl_init_vhost () from /home/bozy/src/mod_perl-1.99_14/src/modules/perl/mod_perl.so
(gdb) bt
#0 0xd0f592ec in modperl_init_vhost () from /home/bozy/src/mod_perl-1.99_14/src/modules/perl/mod_perl.so
#1 0xd0f61d34 in modperl_cmd_modules () from /home/bozy/src/mod_perl-1.99_14/src/modules/perl/mod_perl.so
#2 0x1000c228 in invoke_cmd (cmd=0x202ce2c0, parms=0x2ff21878, mconfig=0x20297838, args=0x203c37cb "")
at config.c:758
#3 0x1000d060 in ap_walk_config_sub (current=0x203c3798, parms=0x2ff21878, section_vector=0x20241b78)
at config.c:1048
#4 0x1000d164 in ap_walk_config (current=0x203c3798, parms=0x2ff21878, section_vector=0x20241b78)
at config.c:1087
#5 0xd0f4fcf8 in modperl_config_insert () from /home/bozy/src/mod_perl-1.99_14/src/modules/perl/mod_perl.so
#6 0x203c3798 in ?? ()
(gdb) c
Continuing.
Good. Now recompile mod_perl with MP_DEBUG=1, so that the trace will show the line number and the arguments to the calls inside mod_perl.so and try to get a new backtrace. Thanks.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- 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
