Front page | perl.perl5.porters |
Postings from May 2010
I grabbed the logs:
On Sun, May 30, 2010 at 01:01:00AM -0400, George Greer wrote:
> Automated smoke report for 5.13.1 patch c85ae797ecb755d3bcfabd44aa268e3e6e2e7c13 v5.13.1-101-gc85ae79
> perl-win2k: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz(~2755 MHz) (x86/1 cpu)
> on MSWin32 - Win2000 SP4
> using cl version 14.00.50727.762
> smoketime 4 hours 34 minutes (average 34 minutes 18 seconds)
> Failures: (common-args) none
> [default] -Duseithreads
> [default] -DDEBUGGING -Duseithreads
> [default] -Duseithreads -Duselargefiles
> [default] -DDEBUGGING -Duseithreads -Duselargefiles
> ../t/op/magic.t.............................................FAILED
> 84-85
op/lop.t .......................................................... ok
# PROG:
# $DB::single = 2;
# $DB::trace = 4;
# $DB::signal = 8;
# $^P = 0;
# print "$DB::single $DB::trace $DB::signal";
# EXPECTED:
# 2 4 8
# GOT:
# STATUS: -1
# Failed at op/magic.t line 545
# PROG:
# $DB::single = 2;
# $DB::trace = 4;
# $DB::signal = 8;
# $^P = 1;
# print "$DB::single $DB::trace $DB::signal";
# EXPECTED:
# 2 4 8
# GOT:
# STATUS: -1
# Failed at op/magic.t line 545
op/magic.t ........................................................
Failed 2/85 subtests
(less 9 skipped subtests: 74 okay)
What's special about $DB::single, $DB::trace, $DB::signal on Win32 with
ithreads? The test passes without ithreads. It's not exactly complex:
$DB::single = 2;
$DB::trace = 4;
$DB::signal = 8;
$^P = 0; # and then 1 on the second iteration
print "$DB::single $DB::trace $DB::signal";
__END__
It's even failing when $^P is assigned 0. Nothing should happen in that case.
pod/perlport.pod doesn't say anything.
Nicholas Clark
Thread Previous