On Fri, Mar 08, 2002 at 11:26:50AM -0500, daniel.jarboe@custserv.com wrote: > Running RH 7.2 in a test LPAR with perl-5.6.0-17. > > The upgrade to perl-5.6.1 from the SRPM failed because the op/study test > fails, but the same test fails for 5.6.0-17. > > # pwd > /usr/src/redhat/BUILD/perl-5.6.1/t > # ./perl -I../lib harness > -snip- > op/study............dubious > Test returned status 0 (wstat 11, 0xb) > -snip- > Failed Test Status Wstat Total Fail Failed List of Failed > -------------------------------------------------------------------------------- > op/study.t 0 11 ?? ?? % ?? > > > Using perl5.6.0, a '/usr/bin/perl -w > /usr/src/redhat/BUILD/perl-5.6.1/t/op/study.t': > 1..24 > ok 1 > ok 2 > Segmentation fault > > > in /var/log/messages > Mar 8 11:14:42 tcsl kernel: User process fault: interruption code 0x10 > Mar 8 11:14:42 tcsl kernel: failing address: 0 > Mar 8 11:14:42 tcsl kernel: CPU: 0 > Mar 8 11:14:42 tcsl kernel: Process perl (pid: 10369, stackpage=02841000) > Mar 8 11:14:42 tcsl kernel: > Mar 8 11:14:42 tcsl kernel: User PSW: 070df000 804a608c Tainted: P > Mar 8 11:14:42 tcsl kernel: task: 02840000 ksp: 02841cb0 pt_regs: 02841f68 > Mar 8 11:14:42 tcsl kernel: User GPRS: > Mar 8 11:14:42 tcsl kernel: 00300001 ffffffff 00000000 00000000 > Mar 8 11:14:42 tcsl kernel: 00000006 004d2210 7ffff678 004d9f80 > Mar 8 11:14:42 tcsl kernel: 004d9f40 004d2210 004d2210 004d9f80 > Mar 8 11:14:42 tcsl kernel: 00000003 804a5d0c 8045ea08 7ffff610 > Mar 8 11:14:42 tcsl kernel: User ACRS: > Mar 8 11:14:42 tcsl kernel: 00000000 00000000 00000000 00000000 > Mar 8 11:14:42 tcsl last message repeated 3 times > Mar 8 11:14:42 tcsl kernel: User Code: > Mar 8 11:14:42 tcsl kernel: 58 60 20 04 58 30 f0 84 58 20 d0 1c 58 40 > 30 00 58 30 20 00 > > > Commenting out #if ($x =~ /^def/) {print "ok 3\n";} else {print "not ok > 3\n";} > I make it as far as: > 1..24 > ok 1 > ok 2 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > Segmentation fault > > Haven't commented out beyond this. > Anyone else having similar problems? Can you please report this within http://bugzilla.redhat.com/bugzilla for arch S/390? This makes sure we can track update information about this etc. Thanks a lot for reporting this problem, Florian La Roche