[mp2] modperl test failed

[Alex Oboimov]

Hello Stas,

After configuring with MP_DEBUG=1 I've encountered segfault during
configuration itself the diagnostic being exactly the same as during
t/TEST (except for damns :). And after make & t/TEST I've got:

[EMAIL PROTECTED] mod_perl-1.99_14]# t/TEST -verbose api/rflush.t
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl5.8.1 /usr/local/src/mod_perl-1.99_14/t/TEST -verbose 'api/rflush.t'
[warning] root mode: changing the files ownership to 'nobody' (65534:65534)
[warning] testing whether 'nobody' is able to -rwx /usr/local/src/mod_perl-1.99_14/t
"/usr/bin/perl5.8.1" -Mlib=/usr/local/src/mod_perl-1.99_14/Apache-Test/lib -MApache::TestRun -e 'eval { Apache::TestRun::run_root_fs_test(65534, 65534, q[/usr/local/src/mod_perl-1.99_14/t]) }';

[warning] result: OK
[warning] the client side drops 'root' permissions and becomes 'nobody'
/usr/local/apache2/bin/httpd -d /usr/local/src/mod_perl-1.99_14/t -f /usr/local/src/mod_perl-1.99_14/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS
using Apache/2.0.49 (prefork MPM)

waiting 120 seconds for server to start: .................[Tue Jun 15 11:53:23 2004] [info] 27 Apache:: modules loaded
[Tue Jun 15 11:53:23 2004] [info] 5 APR:: modules loaded
[Tue Jun 15 11:53:23 2004] [info] base server + 17 vhosts ready to run tests
....................................
waiting 120 seconds for server to start: ok (waited 51 secs)
server localhost.localdomain:8529 started
server localhost.localdomain:8530 listening (TestModperl::merge)
server localhost.localdomain:8531 listening (TestModperl::perl_options)
server localhost.localdomain:8532 listening (TestModperl::setupenv)
server localhost.localdomain:8533 listening (TestVhost::config)
server localhost.localdomain:8534 listening (TestProtocol::echo_filter)
server localhost.localdomain:8535 listening (TestProtocol::echo_timeout)
server localhost.localdomain:8536 listening (TestProtocol::echo_block)
server localhost.localdomain:8537 listening (TestPreConnection::note)
server localhost.localdomain:8538 listening (TestHooks::stacked_handlers2)
server localhost.localdomain:8539 listening (TestHooks::startup)
server localhost.localdomain:8540 listening (TestFilter::in_bbs_inject_header)

 

....

 

# Running under perl version 5.008001 for linux
# Current time local: Tue Jun 15 11:54:01 2004
# Current time GMT:   Tue Jun 15 06:54:01 2004
# Using Test.pm version 1.24
# testing : rflush creates bucket brigades
# expected: [<foo][bar>][<who][ah>]
# received: [<foo][bar>]
not ok 1
# Failed test 1 in t/api/rflush.t at line 13
FAILED test 1
        Failed 1/1 tests, 0.00% okay
        Failed Test    Stat Wstat Total Fail  Failed  List of Failed
        -------------------------------------------------------------------------------
        t/api/rflush.t                1    1 100.00%  1
        Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
        [warning] server localhost.localdomain:8529 shutdown
        [warning] port 8529 still in use...
        ...done
        [  error] error running tests (please examine t/logs/error_log)
        [   info] an old core file has been found: /usr/local/src/mod_perl-1.99_14/t/core.29457
        [  error] oh dangnabit, server dumped core
        [  error] for stacktrace, run: gdb /usr/local/apache2/bin/httpd -core /usr/local/src/mod_perl-1.99_14/t/core.29626
 
After doing so:
....
(gdb) bt
#0  0x4032fa74 in Perl_pp_leavesub ()
   from /usr/lib/perl5/5.8.1/i386-linux-thread-multi/CORE/libperl.so
   #1  0x082ea5e0 in ?? ()
   #2  0x0918e994 in ?? ()

  

 

As I dare guess the fault is not on the modperl side but on the
   perl's one. So I rather dwell on reinstallation of perl, but my
   early investigation show that it is uneasy task bearing in mind
   complex dependencies of mdk packages. One advice is to run two
   perls - one for system needs and another for apache-perl-modperl
   tier. Is this advisable?

 

>>sure, take your time. but please follow up to the list.

 

Sorry Stas, I press automatically the Respond button and realized it
was your private account afterwards... will never repeat this.

 

Best regards,
 Alex Oboimov

---

ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself