Bug#468327: libapache2-mod-perl2: FTBFS on sparc: oh darn, server dumped core
On Thu, Feb 28, 2008 at 10:01:15PM +0200, Niko Tyni wrote: > On Thu, Feb 28, 2008 at 01:07:18PM +0200, Niko Tyni wrote: > > Package: libapache2-mod-perl2 > > Version: 2.0.3-3 > > Severity: serious > > > > This package failed to build on sparc. From the buildd log: > > > /usr/sbin/apache2 -d > > /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t -f > > /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/conf/httpd.conf > > -D APACHE2 -D PERL_USEITHREADS > > using Apache/2.2.8 (worker MPM) > > > > waiting 180 seconds for server to start: .[ error] > > server has died with status 255 (please examine t/logs/error_log) > > [ error] oh darn, server dumped core > Good news: I'm able to reproduce this both with the selected patches in > 2.0.3-3 and the current upstream SVN snapshot. > It would seem that the SIGBUS is an unaligned access caused by the U32 -> > U16 changes in upstream r615751. I'll rebuild libperl with -g -O0 next > so upstream can look at it better, but that's going to take a while > because my sparc box is quite slow... Here's the better backtrace. I'll forward this upstream tomorrow. Core was generated by `/usr/sbin/apache2 -d /home/buildd/mod-perl2/ModPerl-Registry/t -f /home/buildd/'. Program terminated with signal 10, Bus error. #0 0xf7466914 in Perl_pop_scope (my_perl=0x13e250) at scope.c:143 143 const I32 oldsave = PL_scopestack[--PL_scopestack_ix]; (gdb) bt #0 0xf7466914 in Perl_pop_scope (my_perl=0x13e250) at scope.c:143 #1 0xf7415798 in Perl_pp_entersub (my_perl=0x13e250) at pp_hot.c:2888 #2 0xf73dd87c in Perl_runops_debug (my_perl=0x13e250) at dump.c:1459 #3 0xf7349278 in S_call_body (my_perl=0x13e250, myop=0xff671620, is_eval=1 '\001') at perl.c:2731 #4 0xf7349650 in Perl_eval_sv (my_perl=0x13e250, sv=0x13f898, flags=2) at perl.c:2793 #5 0xf7349ea8 in Perl_require_pv (my_perl=0x13e250, pv=0xfb3e0 "/home/buildd/mod-perl2/ModPerl-Registry/t/conf/modperl_extra_startup.pl") at perl.c:2887 #6 0xf7559304 in modperl_require_file (my_perl=0x13e250, pv=0xfb3e0 "/home/buildd/mod-perl2/ModPerl-Registry/t/conf/modperl_extra_startup.pl", logfailure=1) at modperl_util.c:48 #7 0xf755281c in modperl_config_apply_PerlRequire (s=0x84640, scfg=0xc8178, perl=0x13e250, p=0x7e0c8) at modperl_config.c:427 #8 0xf7550704 in modperl_startup (s=0x84640, p=0x7e0c8) at mod_perl.c:327 #9 0xf75504b4 in modperl_startup (s=0x84640, p=0x7e0c8) at mod_perl.c:207 #10 0xf7550988 in modperl_init (base_server=0x84640, p=0x7e0c8) at mod_perl.c:458 #11 0xf7550b14 in modperl_hook_init (pconf=0x7e0c8, plog=0xb0190, ptemp=0xb2198, s=0x84640) at mod_perl.c:631 #12 0x0003f620 in ap_run_open_logs () #13 0x0002ce8c in main () Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468327: libapache2-mod-perl2: FTBFS on sparc: oh darn, server dumped core
On Thu, Feb 28, 2008 at 01:07:18PM +0200, Niko Tyni wrote: > Package: libapache2-mod-perl2 > Version: 2.0.3-3 > Severity: serious > > This package failed to build on sparc. From the buildd log: > /usr/sbin/apache2 -d > /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t -f > /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/conf/httpd.conf > -D APACHE2 -D PERL_USEITHREADS > using Apache/2.2.8 (worker MPM) > > waiting 180 seconds for server to start: .[ error] > server has died with status 255 (please examine t/logs/error_log) > [ error] oh darn, server dumped core > Maybe we should upgrade to a full current upstream SVN snapshot first... Good news: I'm able to reproduce this both with the selected patches in 2.0.3-3 and the current upstream SVN snapshot. Core was generated by `/usr/sbin/apache2 -d /home/buildd/mod-perl2/ModPerl-Registry/t -f /home/buildd/'. Program terminated with signal 10, Bus error. #0 0x70b6637c in Perl_pop_scope () from /usr/lib/libperl.so.5.8 (gdb) bt #0 0x70b6637c in Perl_pop_scope () from /usr/lib/libperl.so.5.8 #1 0x70b36b50 in Perl_pp_entersub () from /usr/lib/libperl.so.5.8 #2 0x70b351ac in Perl_runops_standard () from /usr/lib/libperl.so.5.8 #3 0x70ad4cb8 in S_call_body () from /usr/lib/libperl.so.5.8 #4 0x70ad4fac in Perl_eval_sv () from /usr/lib/libperl.so.5.8 #5 0x70ad518c in Perl_require_pv () from /usr/lib/libperl.so.5.8 #6 0x70a792d0 in modperl_require_file (my_perl=0x13e258, pv=0xfb4f0 "/tmp/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/conf/modperl_extra_startup.pl", logfailure=1) at modperl_util.c:48 #7 0x70a727c0 in modperl_config_apply_PerlRequire (s=0x84640, scfg=0xc81d0, perl=0x13e258, p=0x7e0c8) at modperl_config.c:432 #8 0x70a706e0 in modperl_startup (s=0x84640, p=0x7e0c8) at mod_perl.c:328 #9 0x70a70490 in modperl_startup (s=0x84640, p=0x7e0c8) at mod_perl.c:208 #10 0x70a70964 in modperl_init (base_server=0x84640, p=0x7e0c8) at mod_perl.c:459 #11 0x70a70af0 in modperl_hook_init (pconf=0x7e0c8, plog=0xb0190, ptemp=0xb2198, s=0x84640) at mod_perl.c:636 #12 0x0003f620 in ap_run_open_logs () #13 0x0002ce8c in main () It would seem that the SIGBUS is an unaligned access caused by the U32 -> U16 changes in upstream r615751. I'll rebuild libperl with -g -O0 next so upstream can look at it better, but that's going to take a while because my sparc box is quite slow... Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468327: libapache2-mod-perl2: FTBFS on sparc: oh darn, server dumped core
Package: libapache2-mod-perl2 Version: 2.0.3-3 Severity: serious This package failed to build on sparc. From the buildd log: ulimit -c unlimited; /usr/bin/perl /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/TEST -bugreport -verbose=0 /usr/sbin/apache2 -d /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t -f /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.2.8 (worker MPM) waiting 180 seconds for server to start: .[ error] server has died with status 255 (please examine t/logs/error_log) [ error] oh darn, server dumped core [ error] for stacktrace, run: gdb /usr/sbin/apache2 -core /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/core sh: line 1: 17602 Terminated /usr/bin/perl /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/TEST -bugreport -verbose=0 make[2]: *** [run_tests] Error 143 make[2]: Leaving directory `/build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry' make[1]: *** [run_tests] Error 2 make[1]: Leaving directory `/build/buildd/libapache2-mod-perl2-2.0.3' make: *** [build-stamp] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 Other architectures seem to be OK, at least those that are built so far. As 2.0.3-2 built fine, this is possibly/probably a problem with the Perl 5.10 patches introduced in -3 that were cherry-picked from the upstream SVN. Maybe we should upgrade to a full current upstream SVN snapshot first... Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
