Front page | perl.perl5.porters |
Postings from September 2016
On Sun Sep 04 11:47:06 2016, dcollinsn@gmail.com wrote: > On Sun Sep 04 11:20:29 2016, sprout wrote: > > On Sun Sep 04 11:06:08 2016, dcollinsn@gmail.com wrote: > > > ./miniperl -e 'CORE::evalbytes S' > > > Segmentation fault > > > > It doesn’t crash for me. > > It crashed for me on both Linux and FreeBSD 10.3. "./miniperl", "./perl" and "perl" (5.24.0) all crashed. [snip] > > Attached patch produces the following: > > $ perl t/op/evalbytes.t > 1..9 > ok 1 - evalbytes outside feature scope > ok 2 - evalbytes basic sanity check > ok 3 - evalbytes on extra-ASCII bytes > ok 4 - evalbytes on upgraded extra-ASCII > ok 5 - evalbytes ignores outer utf8 pragma > ok 6 - use utf8 within evalbytes > ok 7 - use utf8 within evalbytes on utf8 string > ok 8 - evalbytes croaks on non-bytes > Segmentation fault > $ ./perl -Ilib t/op/evalbytes.t > 1..9 > ok 1 - evalbytes outside feature scope > ok 2 - evalbytes basic sanity check > ok 3 - evalbytes on extra-ASCII bytes > ok 4 - evalbytes on upgraded extra-ASCII > ok 5 - evalbytes ignores outer utf8 pragma > ok 6 - use utf8 within evalbytes > ok 7 - use utf8 within evalbytes on utf8 string > ok 8 - evalbytes croaks on non-bytes > ok 9 - [RT \#129196] evalbytes S should not segfault When I tried out this patch on both of my OSes, I got failures: On Linux, where I ran make test_harness: ##### Test Summary Report ------------------- op/evalbytes.t (Wstat: 139 Tests: 0 Failed: 0) Non-zero wait status: 139 Parse errors: No plan found in TAP output ##### On FreeBSD, where I ran 'make test_prep' and then said ##### [perl] $ cd t; ./perl harness -v op/evalbytes.t; cd - No subtests run Test Summary Report ------------------- op/evalbytes.t (Wstat: 139 Tests: 0 Failed: 0) Non-zero wait status: 139 Parse errors: No plan found in TAP output Files=1, Tests=0, 1 wallclock secs ( 0.01 usr 0.00 sys + 0.00 cusr 0.06 csys = 0.07 CPU) Result: FAIL ##### But on each OS, when I simply run the test file with the newly built perl, I get failures: ##### [perl] $ ./perl t/op/evalbytes.t 1..9 ok 1 - evalbytes outside feature scope ok 2 - evalbytes basic sanity check ok 3 - evalbytes on extra-ASCII bytes ok 4 - evalbytes on upgraded extra-ASCII ok 5 - evalbytes ignores outer utf8 pragma ok 6 - use utf8 within evalbytes ok 7 - use utf8 within evalbytes on utf8 string ok 8 - evalbytes croaks on non-bytes Segmentation fault (core dumped) ##### So the patch does not appear to correct the problem on these OSes. Thank you very much. -- James E Keenan (jkeenan@cpan.org) --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=129196Thread Next